{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-16401 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16401 is a medium-severity vulnerability in n/a, published on 6 Nov 2019. 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-2019-16401 and fix it if it is affected.\n\nWhat it is: CVE-2019-16401 is a medium-severity vulnerability in n/a, published on 6 Nov 2019. 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-2019-16401 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-16401/ (Markdown: https://insights.sbomify.com/CVE-2019-16401/index.md)","id":"CVE-2019-16401","markdown":"https://insights.sbomify.com/CVE-2019-16401/index.md","name":"CVE-2019-16401","record":{"aliases":["GHSA-m9qf-97qm-v2vg"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Galaxy devices","requires_auth":"none","summary":"Attackers can inject AT commands over Bluetooth to leak sensitive device information like IMSI and IMEI from vulnerable Samsung Galaxy devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"galaxy_note_2_firmware","vendor":"samsung"},{"product":"galaxy_s3_firmware","vendor":"samsung"},{"product":"galaxy_s8_plus_firmware","vendor":"samsung"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Samsung Galaxy S8 plus (Android version: 8.0.0, Build Number: R16NW.G955USQU5CRG3, Baseband Vendor: Qualcomm Snapdragon 835, Baseband: G955USQU5CRG3), Samsung Galaxy S3 (Android version: 4.3, Build Number: JSS15J.I9300XXUGND5, Baseband Vendor: Samsung Exynos 4412, Baseband: I9300XXUGNA8), and Samsung Galaxy Note 2 (Android version: 4.3, Build Number: JSS15J.I9300XUGND5, Baseband Vendor: Samsung Exynos 4412, Baseband: N7100DDUFND1) devices allow injection of AT+CIMI and AT+CGSN over Bluetooth, leaking sensitive information such as IMSI, IMEI, call status, call setup stage, internet service status, signal strength, current roaming status, battery level, and call held status.","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":"Information disclosure in n/a","id":"CVE-2019-16401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Authorization Bypass Through User-Controlled Key in Bagisto","id":"CVE-2019-16403"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-16400"},"products":["n/a"],"published":"2019-11-06","related":[{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2019-16400","kev_date_added":null,"published":"2019-11-06"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can inject AT commands over Bluetooth to leak sensitive device information like IMSI and IMEI from vulnerable Samsung Galaxy devices.","url":"https://insights.sbomify.com/CVE-2019-16401/"}