{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-53984 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-53984 is a medium-severity denial of service vulnerability in nanopb, published on 2 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53984 and fix it if it is affected.\n\nWhat it is: CVE-2024-53984 is a medium-severity denial of service vulnerability in nanopb, published on 2 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-53984 in the wild and no public exploit code.\n\nAffected product: nanopb. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-53984/ (Markdown: https://insights.sbomify.com/CVE-2024-53984/index.md)","id":"CVE-2024-53984","markdown":"https://insights.sbomify.com/CVE-2024-53984/index.md","name":"CVE-2024-53984","record":{"aliases":["DEBIAN-CVE-2024-53984","GHSA-xwqq-qxmw-hj5r","UBUNTU-CVE-2024-53984","openSUSE-SU-2024:0400-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Nanopb Protocol Buffers","requires_auth":"low_privilege","summary":"Attackers can cause memory leaks and denial of service in Nanopb by exploiting specific decoding conditions with custom stream callbacks.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"},{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"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.","ecosystems":["SUSE:Package Hub 15 SP6","openSUSE:Leap 15.6"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nanopb does not release memory on error return when using PB_DECODE_DELIMITED","id":"CVE-2024-53984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Possible XSS vulnerability with certain configurations of rails-html-sanitizer 1.6.0","id":"CVE-2024-53985"},"packages":[{"ecosystem":"SUSE:Package Hub 15 SP6","fixed":["0.4.6-bp156.4.3.1"],"introduced":["0"],"last_affected":[],"package":"nanopb","purl":"pkg:rpm/suse/nanopb\u0026distro=SUSE%20Package%20Hub%2015%20SP6","source":"openSUSE-SU-2024:0400-1"},{"ecosystem":"openSUSE:Leap 15.6","fixed":["0.4.6-bp156.4.3.1"],"introduced":["0"],"last_affected":[],"package":"nanopb","purl":"pkg:rpm/opensuse/nanopb\u0026distro=openSUSE%20Leap%2015.6","source":"openSUSE-SU-2024:0400-1"}],"prev":{"headline":"Server-side request forgery in Backstage Scaffolder plugin","id":"CVE-2024-53983"},"products":["nanopb"],"published":"2024-12-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-02","vendors":["nanopb"]},"summary":"Attackers can cause memory leaks and denial of service in Nanopb by exploiting specific decoding conditions with custom stream callbacks.","url":"https://insights.sbomify.com/CVE-2024-53984/"}