{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-28387 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28387 is a medium-severity vulnerability in n/a, published on 8 Jun 2022. 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-2022-28387 and fix it if it is affected.\n\nWhat it is: CVE-2022-28387 is a medium-severity vulnerability in n/a, published on 8 Jun 2022. 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-2022-28387 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-2022-28387/ (Markdown: https://insights.sbomify.com/CVE-2022-28387/index.md)","id":"CVE-2022-28387","markdown":"https://insights.sbomify.com/CVE-2022-28387/index.md","name":"CVE-2022-28387","record":{"aliases":["GHSA-xmmw-wq4f-3pw5"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Verbatim secure drives","requires_auth":"none","summary":"Attackers can bypass authentication on Verbatim secure drives using an undocumented IOCTL command to retrieve the password and access stored data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"executive_fingerprint_secure_ssd_firmware","vendor":"verbatim"},{"product":"fingerprint_secure_portable_hard_drive_firmware","vendor":"verbatim"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in certain Verbatim drives through 2022-03-31. Due to an insecure design, they can be unlocked by an attacker who can then gain unauthorized access to the stored data. The attacker can simply use an undocumented IOCTL command that retrieves the correct password. This affects Executive Fingerprint Secure SSD GDMSFE01-INI3637-C VER1.1 and Fingerprint Secure Portable Hard Drive Part Number #53650.","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":"Security feature bypass in n/a","id":"CVE-2022-28387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"Use after free in n/a","id":"CVE-2022-28388"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2022-28386"},"products":["n/a"],"published":"2022-06-08","related":[{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2022-28382","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":6.8,"headline":"Supply chain in n/a","id":"CVE-2022-28383","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":4.6,"headline":"Supply chain in n/a","id":"CVE-2022-28385","kev_date_added":null,"published":"2022-06-08"}],"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-03","vendors":["n/a"]},"summary":"Attackers can bypass authentication on Verbatim secure drives using an undocumented IOCTL command to retrieve the password and access stored data.","url":"https://insights.sbomify.com/CVE-2022-28387/"}