{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2025-21043 in the wild since at least 2 Oct 2025.","fix":"No fix has been published for CVE-2025-21043 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 Oct 2025.","what":"CVE-2025-21043 is a high-severity memory corruption vulnerability in Samsung Android, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-21043 and fix it if it is affected.\n\nWhat it is: CVE-2025-21043 is a high-severity memory corruption vulnerability in Samsung Android, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: Yes. Attackers have exploited CVE-2025-21043 in the wild since at least 2 Oct 2025.\n\nAffected product: Samsung Android. 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-2025-21043/ (Markdown: https://insights.sbomify.com/CVE-2025-21043/index.md)","id":"CVE-2025-21043","markdown":"https://insights.sbomify.com/CVE-2025-21043/index.md","name":"CVE-2025-21043","record":{"aliases":["GHSA-h4h8-5cww-x7j2"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung mobile devices","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via an out-of-bounds write in the image codec library on Samsung mobile devices.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"android","vendor":"samsung"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out-of-bounds write in libimagecodec.quram.so prior to SMR Sep-2025 Release 1 allows remote attackers to execute arbitrary code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Samsung Mobile Devices Out-of-Bounds Write","id":"CVE-2025-21043","indexable":true,"kev":{"dateAdded":"2025-10-02","dueDate":"2025-10-23","knownRansomwareCampaignUse":"Unknown","product":"Mobile Devices","requiredAction":"Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.","vendorProject":"Samsung","vulnerabilityName":"Samsung Mobile Devices Out-of-Bounds Write Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"samsung:android","products":["samsung:android"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Samsung Mobile Devices","id":"CVE-2025-21044"},"packages":[],"prev":{"headline":"Samsung Mobile Devices Out-of-Bounds Write","id":"CVE-2025-21042"},"products":["Samsung Mobile Devices"],"published":"2025-09-12","related":[{"cvss_score":8.8,"headline":"Samsung Mobile Devices Out-of-Bounds Write","id":"CVE-2025-21042","kev_date_added":"2025-11-10","published":"2025-09-12"},{"cvss_score":7.3,"headline":"Samsung Mobile Devices Out-of-Bounds Read","id":"CVE-2021-25487","kev_date_added":"2023-06-29","published":"2021-10-06"},{"cvss_score":6.4,"headline":"Samsung Mobile Devices Race Condition","id":"CVE-2021-25394","kev_date_added":"2023-06-29","published":"2021-06-11"},{"cvss_score":6.4,"headline":"Samsung Mobile Devices Race Condition","id":"CVE-2021-25395","kev_date_added":"2023-06-29","published":"2021-06-11"},{"cvss_score":6.2,"headline":"Samsung Mobile Devices Improper Access Control","id":"CVE-2021-25369","kev_date_added":"2022-11-08","published":"2021-03-26"},{"cvss_score":6.1,"headline":"Samsung Mobile Devices Memory Corruption","id":"CVE-2021-25370","kev_date_added":"2022-11-08","published":"2021-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Samsung Mobile"]},"summary":"Remote attackers can execute arbitrary code via an out-of-bounds write in the image codec library on Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2025-21043/"}