[15:35] Another bad date ("unknown") popped up in the OVAL XML for CVE-2022-32886 on 20.04 [15:35] A buffer overflow issue was addressed with improved memory handling. This issue is fixed in Safari 16, iOS 16, iOS 15.7 and iPadOS 15.7. Processing maliciously crafted web content may lead to arbitrary code execution. [15:37] would it be possible for the generator to attempt to parse the dates it creates? [15:54] hank, it could, but then what? this shouldn't stop the process from generating the data imho [15:54] I think this is something to be fixed in CVE generation, or avoided during CVE generation [15:59] hank, what kind of issues is the date causing to you? [16:16] I mean, if the generator is producing a bogus date, that's something to alert on [16:17] I ask because this has happened multiple times, and could be noticed during the generation process if it just tried to read what it creates [16:18] the problem this causes to me is that my software is parsing the OVAL feed and erroring out because "unknown" isn't any sort of valid date [16:27] hank, the generator is not producing a bogus date, it comes from CVE file: https://git.launchpad.net/ubuntu-cve-tracker/tree/active/CVE-2022-32886 ... the OVAL data is still a valid one with this bogus date (oscap oval validate will succeed) [16:27] A buffer overflow issue was addressed with improved memory handling. This issue is fixed in Safari 16, iOS 16, iOS 15.7 and iPadOS 15.7. Processing maliciously crafted web content may lead to arbitrary code execution. [16:28] hank, which software are you using? [16:37] my colleague fixed the CVE date status, should take a few hours to have this reflected in OVAL [16:37] I will personally take a look tomorrow on what is happening with the CVE generation to create this bogus date [16:53] Clair, but the code handling this is specifically https://github.com/quay/goval-parser/blob/master/oval/types.go#L134