{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51643 exists.","fix":"No fix has been published for CVE-2025-51643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51643 is a low-severity vulnerability in n/a, published on 28 Aug 2025. 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-2025-51643 and fix it if it is affected.\n\nWhat it is: CVE-2025-51643 is a low-severity vulnerability in n/a, published on 28 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51643 exists.\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-2025-51643/ (Markdown: https://insights.sbomify.com/CVE-2025-51643/index.md)","id":"CVE-2025-51643","markdown":"https://insights.sbomify.com/CVE-2025-51643/index.md","name":"CVE-2025-51643","record":{"aliases":["GHSA-5mh7-cqvw-mcp7"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GPS Tracker","requires_auth":"none","summary":"Physical attackers can extract firmware and sensitive credentials from Meitrack GPS trackers via unprotected SPI flash access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"t366l-g_firmware","vendor":"meitrack"}],"cvss":{"score":2.4,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Meitrack T366G-L GPS Tracker devices contain an SPI flash chip (Winbond 25Q64JVSIQ) that is accessible without authentication or tamper protection. An attacker with physical access to the device can use a standard SPI programmer to extract the firmware using flashrom. This results in exposure of sensitive configuration data such as APN credentials, backend server information, and network parameter","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-08-11","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-11T19:22:19Z","kind":"github_poc","ref":"https://github.com/NastyCrow/CVE-2025-51643","stars":1,"title":null}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2025-51643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2025-51650"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-51630"},"products":["n/a"],"published":"2025-08-28","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-28","vendors":["n/a"]},"summary":"Physical attackers can extract firmware and sensitive credentials from Meitrack GPS trackers via unprotected SPI flash access.","url":"https://insights.sbomify.com/CVE-2025-51643/"}