mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-08-04 08:44:25 +00:00
72 lines
2.5 KiB
JSON
72 lines
2.5 KiB
JSON
{
|
|
"CVE_data_meta": {
|
|
"ASSIGNER": "cve@mitre.org",
|
|
"ID": "CVE-2020-24240",
|
|
"STATE": "PUBLIC"
|
|
},
|
|
"affects": {
|
|
"vendor": {
|
|
"vendor_data": [
|
|
{
|
|
"product": {
|
|
"product_data": [
|
|
{
|
|
"product_name": "n/a",
|
|
"version": {
|
|
"version_data": [
|
|
{
|
|
"version_value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
},
|
|
"vendor_name": "n/a"
|
|
}
|
|
]
|
|
}
|
|
},
|
|
"data_format": "MITRE",
|
|
"data_type": "CVE",
|
|
"data_version": "4.0",
|
|
"description": {
|
|
"description_data": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "GNU Bison before 3.7.1 has a use-after-free in _obstack_free in lib/obstack.c (called from gram_lex) when a '\\0' byte is encountered. NOTE: there is a risk only if Bison is used with untrusted input, and the observed bug happens to cause unsafe behavior with a specific compiler/architecture. The bug report was intended to show that a crash may occur in Bison itself, not that a crash may occur in code that is generated by Bison."
|
|
}
|
|
]
|
|
},
|
|
"problemtype": {
|
|
"problemtype_data": [
|
|
{
|
|
"description": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references": {
|
|
"reference_data": [
|
|
{
|
|
"url": "https://github.com/akimd/bison/commit/be95a4fe2951374676efc9454ffee8638faaf68d",
|
|
"refsource": "MISC",
|
|
"name": "https://github.com/akimd/bison/commit/be95a4fe2951374676efc9454ffee8638faaf68d"
|
|
},
|
|
{
|
|
"url": "https://lists.gnu.org/r/bug-bison/2020-07/msg00051.html",
|
|
"refsource": "MISC",
|
|
"name": "https://lists.gnu.org/r/bug-bison/2020-07/msg00051.html"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://github.com/akimd/bison/compare/v3.7...v3.7.1",
|
|
"url": "https://github.com/akimd/bison/compare/v3.7...v3.7.1"
|
|
}
|
|
]
|
|
}
|
|
} |