{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2010-0222 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-0222 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-0222 is a medium-severity vulnerability in n/a, published on 7 Jan 2010. 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-2010-0222 and fix it if it is affected.\n\nWhat it is: CVE-2010-0222 is a medium-severity vulnerability in n/a, published on 7 Jan 2010. 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-2010-0222 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-2010-0222/ (Markdown: https://insights.sbomify.com/CVE-2010-0222/index.md)","id":"CVE-2010-0222","markdown":"https://insights.sbomify.com/CVE-2010-0222/index.md","name":"CVE-2010-0222","record":{"aliases":["GHSA-5chj-892r-cfh4"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"USB flash drive","requires_auth":"none","summary":"Attackers with physical access can read or modify data on Kingston USB drives by using a fixed hardcoded encryption key.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"datatraveler_blackbox","vendor":"kingston"},{"product":"datatraveler_elite","vendor":"kingston"},{"product":"datatraveler_secure","vendor":"kingston"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"Kingston DataTraveler BlackBox (DTBB), DataTraveler Secure Privacy Edition (DTSP), and DataTraveler Elite Privacy Edition (DTEP) USB flash drives use a fixed 256-bit key for obtaining access to the cleartext drive contents, which makes it easier for physically proximate attackers to read or modify data by determining and providing this key.","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":"Hardcoded credentials in n/a","id":"CVE-2010-0222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2010"},"n_packages":0,"n_references":9,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2010-0223"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2010-0221"},"products":["n/a"],"published":"2010-01-07","related":[{"cvss_score":2.1,"headline":"Security feature bypass in n/a","id":"CVE-2010-0221","kev_date_added":null,"published":"2010-01-07"},{"cvss_score":2.1,"headline":"Security feature bypass in n/a","id":"CVE-2010-0223","kev_date_added":null,"published":"2010-01-07"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers with physical access can read or modify data on Kingston USB drives by using a fixed hardcoded encryption key.","url":"https://insights.sbomify.com/CVE-2010-0222/"}