mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-08-04 08:44:25 +00:00
82 lines
3.0 KiB
JSON
82 lines
3.0 KiB
JSON
{
|
|
"data_type": "CVE",
|
|
"data_format": "MITRE",
|
|
"data_version": "4.0",
|
|
"CVE_data_meta": {
|
|
"ID": "CVE-2024-34581",
|
|
"ASSIGNER": "cve@mitre.org",
|
|
"STATE": "PUBLIC"
|
|
},
|
|
"affects": {
|
|
"vendor": {
|
|
"vendor_data": [
|
|
{
|
|
"product": {
|
|
"product_data": [
|
|
{
|
|
"product_name": "n/a",
|
|
"version": {
|
|
"version_data": [
|
|
{
|
|
"version_value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
},
|
|
"vendor_name": "n/a"
|
|
}
|
|
]
|
|
}
|
|
},
|
|
"problemtype": {
|
|
"problemtype_data": [
|
|
{
|
|
"description": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references": {
|
|
"reference_data": [
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://www.w3.org/TR/xmldsig-core2/",
|
|
"url": "https://www.w3.org/TR/xmldsig-core2/"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://www.w3.org/TR/xmldsig-core1/",
|
|
"url": "https://www.w3.org/TR/xmldsig-core1/"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://www.w3.org/TR/2013/NOTE-xmldsig-bestpractices-20130411/",
|
|
"url": "https://www.w3.org/TR/2013/NOTE-xmldsig-bestpractices-20130411/"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://www.w3.org/Signature/Drafts/WD-xmldsig-core-200003plc/",
|
|
"url": "https://www.w3.org/Signature/Drafts/WD-xmldsig-core-200003plc/"
|
|
},
|
|
{
|
|
"refsource": "MISC",
|
|
"name": "https://github.com/zmanion/Vulnerabilities/blob/main/CVE-2024-21893.md",
|
|
"url": "https://github.com/zmanion/Vulnerabilities/blob/main/CVE-2024-21893.md"
|
|
}
|
|
]
|
|
},
|
|
"description": {
|
|
"description_data": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "The W3C XML Signature Syntax and Processing (XMLDsig) specification, starting with 1.0, was originally published with a \"RetrievalMethod is a URI ... that may be used to obtain key and/or certificate information\" statement and no accompanying information about SSRF risks, and this may have contributed to vulnerable implementations such as those discussed in CVE-2023-36661 and CVE-2024-21893. NOTE: this was mitigated in 1.1 and 2.0 via a directly referenced Best Practices document that calls on implementers to be wary of SSRF."
|
|
}
|
|
]
|
|
}
|
|
} |