{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2022-28382 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28382 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28382 is a high-severity vulnerability in n/a, published on 8 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-28382 and fix it if it is affected.\n\nWhat it is: CVE-2022-28382 is a high-severity vulnerability in n/a, published on 8 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-28382 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-28382/ (Markdown: https://insights.sbomify.com/CVE-2022-28382/index.md)","id":"CVE-2022-28382","markdown":"https://insights.sbomify.com/CVE-2022-28382/index.md","name":"CVE-2022-28382","record":{"aliases":["GHSA-73wv-q9rq-5crw"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Verbatim secure drives","requires_auth":"none","summary":"Insecure AES-ECB encryption in Verbatim drive firmware allows attackers to extract sensitive information from encrypted data by observing repeating patterns.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"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"},{"product":"keypad_secure_usb_3.2_gen_1_firmware","vendor":"verbatim"},{"product":"store_\\'n\\'_go_secure_portable_hdd_firmware","vendor":"verbatim"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"An issue was discovered in certain Verbatim drives through 2022-03-31. Due to the use of an insecure encryption AES mode (Electronic Codebook, aka ECB), an attacker may be able to extract information even from encrypted data, for example by observing repeating byte patterns. The firmware of the USB-to-SATA bridge controller INIC-3637EN uses AES-256 with the ECB mode. This operation mode of block ciphers (e.g., AES) always encrypts identical plaintext data, in this case blocks of 16 bytes, to identical ciphertext data. For some data, for instance bitmap images, the lack of the cryptographic property called diffusion, within ECB, can leak sensitive information even in encrypted data. Thus, the use of the ECB operation mode can put the confidentiality of specific information at risk, even in an encrypted form. This affects Keypad Secure USB 3.2 Gen 1 Drive Part Number #49428, Store 'n' Go Secure Portable HDD GD25LK01-3637-C VER4.0, 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":"Weak cryptography in n/a","id":"CVE-2022-28382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":14,"next":{"headline":"Supply chain in n/a","id":"CVE-2022-28383"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-28381"},"products":["n/a"],"published":"2022-06-08","related":[{"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"},{"cvss_score":4.6,"headline":"Security feature bypass in n/a","id":"CVE-2022-28387","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":"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-03","vendors":["n/a"]},"summary":"Insecure AES-ECB encryption in Verbatim drive firmware allows attackers to extract sensitive information from encrypted data by observing repeating patterns.","url":"https://insights.sbomify.com/CVE-2022-28382/"}