{"answers":{"affected":"1 open source package ship an affected version, including github.com/mcu-tools/mcuboot.","exploited":"There is no known exploitation of CVE-2024-32883 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-32883 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-32883 is a high-severity vulnerability in mcu-tools mcuboot, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-32883 and fix it if it is affected.\n\nWhat it is: CVE-2024-32883 is a high-severity vulnerability in mcu-tools mcuboot, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-32883 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/mcu-tools/mcuboot (Go): affected all versions; no fix listed\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-32883/ (Markdown: https://insights.sbomify.com/CVE-2024-32883/index.md)","id":"CVE-2024-32883","markdown":"https://insights.sbomify.com/CVE-2024-32883/index.md","name":"CVE-2024-32883","record":{"aliases":["GO-2024-2799"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MCUboot secure bootloader","requires_auth":"low_privilege","summary":"Attackers can inject unprotected TLV entries into MCUboot images, potentially bypassing security checks or altering attestation records.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"MCUboot is a secure bootloader for 32-bits microcontrollers. MCUboot uses a TLV (tag-length-value) structure to represent the meta data associated with an image.  The TLVs themselves are divided into two sections, a protected and an unprotected section. The protected TLV entries are included as part of the image signature to avoid tampering. However, the code does not distinguish which TLV entries should be protected or not, so it is possible for an attacker to add unprotected TLV entries that should be protected. Currently, the primary protected TLV entries should be the dependency indication, and the boot record. An injected dependency value would primarily result in an otherwise acceptable image being rejected. A boot record injection could allow fields in a later attestation record to include data not intended, which could cause an image to appear to have properties that it should not have. As a workaround, disable the boot record functionality.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MCUboot Injection attack of unprotected TLV values","id":"CVE-2024-32883","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2024"},"n_packages":1,"n_references":1,"next":{"headline":"gix-transport indirect code execution via malicious username","id":"CVE-2024-32884"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/mcu-tools/mcuboot","purl":"pkg:golang/github.com/mcu-tools/mcuboot","source":"GO-2024-2799"}],"prev":{"headline":"Permission check bypass when editing a model with per-field restrictions in wagtail","id":"CVE-2024-32882"},"products":["mcuboot"],"published":"2024-04-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-08-02","vendors":["mcu-tools"]},"summary":"Attackers can inject unprotected TLV entries into MCUboot images, potentially bypassing security checks or altering attestation records.","url":"https://insights.sbomify.com/CVE-2024-32883/"}