{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2023-21492 in the wild since at least 19 May 2023.","fix":"No fix has been published for CVE-2023-21492 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Jun 2023.","what":"CVE-2023-21492 is a medium-severity vulnerability in Samsung Android, published on 4 May 2023. 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-2023-21492 and fix it if it is affected.\n\nWhat it is: CVE-2023-21492 is a medium-severity vulnerability in Samsung Android, published on 4 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2023-21492 in the wild since at least 19 May 2023.\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-2023-21492/ (Markdown: https://insights.sbomify.com/CVE-2023-21492/index.md)","id":"CVE-2023-21492","markdown":"https://insights.sbomify.com/CVE-2023-21492/index.md","name":"CVE-2023-21492","record":{"aliases":["GHSA-v36x-x4cv-7vr2"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung mobile OS","requires_auth":"high_privilege","summary":"A privileged local attacker can read kernel pointers from logs to bypass ASLR on Samsung mobile devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"android","vendor":"samsung"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Kernel pointers are printed in the log file prior to SMR May-2023 Release 1 allows a privileged local attacker to bypass ASLR.","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 Insertion of Sensitive Information Into Log File","id":"CVE-2023-21492","indexable":true,"kev":{"dateAdded":"2023-05-19","dueDate":"2023-06-09","knownRansomwareCampaignUse":"Unknown","product":"Mobile Devices","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Samsung","vulnerabilityName":"Samsung Mobile Devices Insertion of Sensitive Information Into Log File Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"samsung:android","products":["samsung:android"],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2023-21493"},"packages":[],"prev":{"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2023-21491"},"products":["Samsung Mobile Devices"],"published":"2023-05-04","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":8.8,"headline":"Samsung Mobile Devices Out-of-Bounds Write","id":"CVE-2025-21043","kev_date_added":"2025-10-02","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":"partial"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Samsung Mobile"]},"summary":"A privileged local attacker can read kernel pointers from logs to bypass ASLR on Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2023-21492/"}