mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-07-29 05:56:59 +00:00
77 lines
2.8 KiB
JSON
77 lines
2.8 KiB
JSON
{
|
|
"data_type": "CVE",
|
|
"data_format": "MITRE",
|
|
"data_version": "4.0",
|
|
"CVE_data_meta": {
|
|
"ID": "CVE-2021-20303",
|
|
"ASSIGNER": "secalert@redhat.com",
|
|
"STATE": "PUBLIC"
|
|
},
|
|
"affects": {
|
|
"vendor": {
|
|
"vendor_data": [
|
|
{
|
|
"vendor_name": "n/a",
|
|
"product": {
|
|
"product_data": [
|
|
{
|
|
"product_name": "OpenEXR",
|
|
"version": {
|
|
"version_data": [
|
|
{
|
|
"version_value": "Fixed in v2.5.4 and beyond."
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
}
|
|
},
|
|
"problemtype": {
|
|
"problemtype_data": [
|
|
{
|
|
"description": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "CWE-190 - Integer Overflow or Wraparound, CWE-787 - Out-of-bounds Write"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references": {
|
|
"reference_data": [
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://bugzilla.redhat.com/show_bug.cgi?id=1939151",
|
|
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1939151"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25505",
|
|
"url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25505"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://github.com/AcademySoftwareFoundation/openexr/pull/831",
|
|
"url": "https://github.com/AcademySoftwareFoundation/openexr/pull/831"
|
|
},
|
|
{
|
|
"refsource": "MLIST",
|
|
"name": "[debian-lts-announce] 20221211 [SECURITY] [DLA 3236-1] openexr security update",
|
|
"url": "https://lists.debian.org/debian-lts-announce/2022/12/msg00022.html"
|
|
}
|
|
]
|
|
},
|
|
"description": {
|
|
"description_data": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "A flaw found in function dataWindowForTile() of IlmImf/ImfTiledMisc.cpp. An attacker who is able to submit a crafted file to be processed by OpenEXR could trigger an integer overflow, leading to an out-of-bounds write on the heap. The greatest impact of this flaw is to application availability, with some potential impact to data integrity as well."
|
|
}
|
|
]
|
|
}
|
|
} |