{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14474 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14474 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14474 is a high-severity vulnerability in n/a, published on 30 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-14474 and fix it if it is affected.\n\nWhat it is: CVE-2020-14474 is a high-severity vulnerability in n/a, published on 30 Jun 2020. 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-2020-14474 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-2020-14474/ (Markdown: https://insights.sbomify.com/CVE-2020-14474/index.md)","id":"CVE-2020-14474","markdown":"https://insights.sbomify.com/CVE-2020-14474/index.md","name":"CVE-2020-14474","record":{"aliases":["GHSA-x3pm-5wjh-h6w2"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cellebrite UFED physical device","requires_auth":"none","summary":"Hardcoded key material in Cellebrite UFED allows attackers to decrypt protected data on devices running affected software versions.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ufed_firmware","vendor":"cellebrite"}],"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-798","name":"Use of Hard-coded Credentials"}],"description":"The Cellebrite UFED physical device 5.0 through 7.5.0.845 relies on key material hardcoded within both the executable code supporting the decryption process, and within the encrypted files themselves by using a key enveloping technique. The recovered key material is the same for every device running the same version of the software, and does not appear to be changed with each new build. It is possible to reconstruct the decryption process using the hardcoded key material and obtain easy access to otherwise protected data.","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-2020-14474","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Dolibarr reflected cross-site scripting (XSS) vulnerability","id":"CVE-2020-14475"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-14473"},"products":["n/a"],"published":"2020-06-30","related":[{"cvss_score":5.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-11723","kev_date_added":null,"published":"2020-04-14"}],"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-04","vendors":["n/a"]},"summary":"Hardcoded key material in Cellebrite UFED allows attackers to decrypt protected data on devices running affected software versions.","url":"https://insights.sbomify.com/CVE-2020-14474/"}