{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28096 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28096 is a medium-severity vulnerability in n/a, published on 28 Dec 2020. 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-2020-28096 and fix it if it is affected.\n\nWhat it is: CVE-2020-28096 is a medium-severity vulnerability in n/a, published on 28 Dec 2020. 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-2020-28096 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-28096/ (Markdown: https://insights.sbomify.com/CVE-2020-28096/index.md)","id":"CVE-2020-28096","markdown":"https://insights.sbomify.com/CVE-2020-28096/index.md","name":"CVE-2020-28096","record":{"aliases":["GHSA-fmh2-qxcv-pr3h"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["account_takeover","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Foscam IP camera","requires_auth":"none","summary":"Attackers with physical UART access can log in using a hardcoded password, leading to full device compromise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"foscam_x1_firmware","vendor":"foscammall"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"FOSCAM FHD X1 1.14.2.4 devices allow attackers (with physical UART access) to login via the ipc.fos~ password.","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-28096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-28097"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-28095"},"products":["n/a"],"published":"2020-12-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers with physical UART access can log in using a hardcoded password, leading to full device compromise.","url":"https://insights.sbomify.com/CVE-2020-28096/"}