{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-42533 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-42533 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42533 is a medium-severity code injection vulnerability in Samsung Android, published on 7 Nov 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-42533 and fix it if it is affected.\n\nWhat it is: CVE-2023-42533 is a medium-severity code injection vulnerability in Samsung Android, published on 7 Nov 2023. 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-2023-42533 in the wild and no public exploit code.\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-42533/ (Markdown: https://insights.sbomify.com/CVE-2023-42533/index.md)","id":"CVE-2023-42533","markdown":"https://insights.sbomify.com/CVE-2023-42533/index.md","name":"CVE-2023-42533","record":{"aliases":["GHSA-fvch-9qg2-pg4f"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung mobile devices","requires_auth":"low_privilege","summary":"A physical attacker can execute arbitrary code in the kernel via improper input validation in the USB Gadget Interface on Samsung mobile devices.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"android","vendor":"samsung"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"Improper Input Validation with USB Gadget Interface prior to SMR Nov-2023 Release 1 allows a physical attacker to execute arbitrary code in Kernel.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Code injection in Samsung Mobile Devices","id":"CVE-2023-42533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:android","products":["samsung:android"],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in Samsung Mobile Devices","id":"CVE-2023-42534"},"packages":[],"prev":{"headline":"Weak cryptography in Samsung Mobile Devices","id":"CVE-2023-42532"},"products":["Samsung Mobile Devices"],"published":"2023-11-07","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":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-04","vendors":["Samsung Mobile"]},"summary":"A physical attacker can execute arbitrary code in the kernel via improper input validation in the USB Gadget Interface on Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2023-42533/"}