CVE-2024-34703

Botan is a C++ cryptography library. X.509 certificates can identify elliptic curves using either an object identifier or using explicit encoding of the parameters. Prior to versions 3.3.0 and 2.19.4, an attacker could present an ECDSA X.509 certificate using explicit encoding where the parameters are very large. The proof of concept used a 16Kbit prime for this purpose. When parsing, the parameter is checked to be prime, causing excessive computation. This was patched in 2.19.4 and 3.3.0 to allow the prime parameter of the elliptic curve to be at most 521 bits. No known workarounds are available. Note that support for explicit encoding of elliptic curve parameters is deprecated in Botan.

CVSS v3 7.5 HIGH

7.5^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://github.com/randombit/botan/commit/08c404b23740babee1f6aa51b54e966029aadee4
https://github.com/randombit/botan/commit/94e9154c143aa5264da6254a6a1be5bc66ee2b5a
https://github.com/randombit/botan/security/advisories/GHSA-w4g2-7m2h-7xj7

Configurations

No configuration.

History

No history.

Information

Published : 2024-06-30 21:15

Updated : 2024-07-01 12:37

NVD link : CVE-2024-34703

Mitre link : CVE-2024-34703

CVE.ORG link : CVE-2024-34703

JSON object : View

Products Affected

No product.

CWE

CWE-405

Asymmetric Resource Consumption (Amplification)

CWE-770

Allocation of Resources Without Limits or Throttling

{"id": "CVE-2024-34703", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2024-06-30T21:15:02.053", "references": [{"url": "https://github.com/randombit/botan/commit/08c404b23740babee1f6aa51b54e966029aadee4", "source": "security-advisories@github.com"}, {"url": "https://github.com/randombit/botan/commit/94e9154c143aa5264da6254a6a1be5bc66ee2b5a", "source": "security-advisories@github.com"}, {"url": "https://github.com/randombit/botan/security/advisories/GHSA-w4g2-7m2h-7xj7", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-405"}, {"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "Botan is a C++ cryptography library. X.509 certificates can identify elliptic curves using either an object identifier or using explicit encoding of the parameters. Prior to versions 3.3.0 and 2.19.4, an attacker could present an ECDSA X.509 certificate using explicit encoding where the parameters are very large. The proof of concept used a 16Kbit prime for this purpose. When parsing, the parameter is checked to be prime, causing excessive computation. This was patched in 2.19.4 and 3.3.0 to allow the prime parameter of the elliptic curve to be at most 521 bits. No known workarounds are available. Note that support for explicit encoding of elliptic curve parameters is deprecated in Botan.\n"}, {"lang": "es", "value": "Botan es una librer\u00eda de criptograf\u00eda C++. Los certificados X.509 pueden identificar curvas el\u00edpticas utilizando un identificador de objeto o una codificaci\u00f3n expl\u00edcita de los par\u00e1metros. Antes de las versiones 3.3.0 y 2.19.4, un atacante pod\u00eda presentar un certificado ECDSA X.509 usando codificaci\u00f3n expl\u00edcita donde los par\u00e1metros eran muy grandes. La prueba de concepto utiliz\u00f3 un prime de 16 Kbit para este prop\u00f3sito. Al analizar, se comprueba que el par\u00e1metro sea primo, lo que provoca un c\u00e1lculo excesivo. Esto fue parcheado en 2.19.4 y 3.3.0 para permitir que el par\u00e1metro principal de la curva el\u00edptica tenga como m\u00e1ximo 521 bits. No hay workarounds disponibles. Tenga en cuenta que la compatibilidad con la codificaci\u00f3n expl\u00edcita de par\u00e1metros de curvas el\u00edpticas est\u00e1 obsoleta en Botan."}], "lastModified": "2024-07-01T12:37:24.220", "sourceIdentifier": "security-advisories@github.com"}