Open jgamblin opened 1 month ago
I think this probably needs to be submitted here: https://github.com/CVEProject/cve-website/issues.
@ccoffin, should the schema not specify the description's length or type as a plain text string, or should \n
, \t
, and extra white spaces and emojis be allowed in descriptions?
I am unsure if these 50+ CVEs are skirting an unenforced requirement or if no one is displaying them correctly.
More and More CVES are starting to contain hidden formatting characters and extra spaces that should likely be supported on CVE.org, or the schema should specify that the description is a unicode string.
I will use CVE-2024-44995 as an example of this issue:
As submitted in the JSON File:
As Rendered in Text:
As Rendered on CVE.org:
Here is a CSV with CVEs that are causing the most issues matching against a string: SpecialDescription.csv