CVE-2024-53984

Nanopb is a small code-size Protocol Buffers implementation. When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.

CVSS v3 4.3 MEDIUM

4.3^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 2.8 / Impact : 1.4

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact LOW

Scope UNCHANGED

References

Link	Resource
https://github.com/nanopb/nanopb/commit/2b86c255aa52250438d5aba124d0e86db495b378
https://github.com/nanopb/nanopb/security/advisories/GHSA-xwqq-qxmw-hj5r

Configurations

No configuration.

History

02 Dec 2024, 16:15

Type	Values Removed	Values Added
New CVE

Information

Published : 2024-12-02 16:15

Updated : 2024-12-02 16:15

NVD link : CVE-2024-53984

Mitre link : CVE-2024-53984

CVE.ORG link : CVE-2024-53984

JSON object : View

Products Affected

No product.

CWE

CWE-401

Missing Release of Memory after Effective Lifetime

CWE-755

Improper Handling of Exceptional Conditions

{"id": "CVE-2024-53984", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.8}]}, "published": "2024-12-02T16:15:14.603", "references": [{"url": "https://github.com/nanopb/nanopb/commit/2b86c255aa52250438d5aba124d0e86db495b378", "source": "security-advisories@github.com"}, {"url": "https://github.com/nanopb/nanopb/security/advisories/GHSA-xwqq-qxmw-hj5r", "source": "security-advisories@github.com"}], "vulnStatus": "Received", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-401"}, {"lang": "en", "value": "CWE-755"}]}], "descriptions": [{"lang": "en", "value": "Nanopb is a small code-size Protocol Buffers implementation. When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1."}, {"lang": "es", "value": "Nanopb es una implementaci\u00f3n de Protocol Buffers de tama\u00f1o de c\u00f3digo peque\u00f1o. Cuando la opci\u00f3n de tiempo de compilaci\u00f3n PB_ENABLE_MALLOC est\u00e1 habilitada, el mensaje contiene al menos un campo con el tipo de campo FT_POINTER, se utiliza una devoluci\u00f3n de llamada de flujo personalizada con una longitud de flujo desconocida y la funci\u00f3n pb_decode_ex() se utiliza con el indicador PB_DECODE_DELIMITED, entonces la funci\u00f3n pb_decode_ex() no llama autom\u00e1ticamente a pb_release(), como se hace para otros casos de falla. Esto podr\u00eda provocar una p\u00e9rdida de memoria y una posible denegaci\u00f3n de servicio. Esta vulnerabilidad se corrigi\u00f3 en la versi\u00f3n 0.4.9.1."}], "lastModified": "2024-12-02T16:15:14.603", "sourceIdentifier": "security-advisories@github.com"}