Files
vuln-cve/data/2024/43xxx/CVE-2024-43372.json
T

31 lines
1.4 KiB
JSON

{
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"cveMetadata": {
"cveId": "CVE-2024-43372",
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"state": "REJECTED",
"dateReserved": "2024-08-09T14:23:55.513Z",
"dateUpdated": "2024-08-19T13:26:30.853Z",
"dateRejected": "2024-08-19T13:26:30.853Z",
"assignerShortName": "GitHub_M"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M",
"dateUpdated": "2024-08-19T13:26:30.853Z"
},
"rejectedReasons": [
{
"lang": "en",
"value": "** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-43369. Reason: This candidate is a duplicate of CVE-2024-43369. Notes: All CVE users should reference CVE-2024-43369 instead of this candidate. This CVE was issued to a vulnerability that is dependent on CVE-2024-43369. According to rule 4.2.15 of the CVE CNA rules, \"CNAs MUST NOT assign a different CVE ID to a Vulnerability that is fully interdependent with another Vulnerability. The Vulnerabilities are effectively the same single Vulnerability and MUST use one CVE ID.\""
}
],
"replacedBy": [
"CVE-2024-43369"
]
}
}
}