{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3891 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3891 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3891 is a medium-severity vulnerability in unknown Yi Technology, published on 2 Nov 2018. 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-2018-3891 and fix it if it is affected.\n\nWhat it is: CVE-2018-3891 is a medium-severity vulnerability in unknown Yi Technology, published on 2 Nov 2018. 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-2018-3891 in the wild and no public exploit code.\n\nAffected product: unknown Yi Technology. 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-2018-3891/ (Markdown: https://insights.sbomify.com/CVE-2018-3891/index.md)","id":"CVE-2018-3891","markdown":"https://insights.sbomify.com/CVE-2018-3891/index.md","name":"CVE-2018-3891","record":{"aliases":["GHSA-2vx9-h65m-6rg8"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yi Home Camera","requires_auth":"none","summary":"An attacker with physical access can downgrade the firmware of Yi Home Cameras by inserting a specially crafted SD card, bypassing update security controls.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"yi_home_camera_firmware","vendor":"yitechnology"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L","version":"3.0"},"cwes":[],"description":"An exploitable firmware downgrade vulnerability exists in the firmware update functionality of Yi Home Camera 27US 1.8.7.0D. A specially crafted file can cause a logic flaw, resulting in a firmware downgrade. An attacker can insert an SD card to trigger this vulnerability.","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 Yi Technology","id":"CVE-2018-3891","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Yi Technology","id":"CVE-2018-3892"},"packages":[],"prev":{"headline":"Command injection in Yi Technology","id":"CVE-2018-3890"},"products":["Yi Technology"],"published":"2018-11-02","related":[{"cvss_score":9.6,"headline":"Memory corruption in Yi Technology","id":"CVE-2018-3892","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":9,"headline":"Auth bypass in Yi Technology","id":"CVE-2018-3934","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":8.3,"headline":"Memory corruption in Yi Technology","id":"CVE-2018-3898","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":8.3,"headline":"Memory corruption in Yi Technology","id":"CVE-2018-3899","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":7.6,"headline":"Command injection in Yi Technology","id":"CVE-2018-3890","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":7.6,"headline":"Code injection in Yi Technology","id":"CVE-2018-3920","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":7.5,"headline":"Denial of service in Yi Technology","id":"CVE-2018-3928","kev_date_added":null,"published":"2018-11-01"}],"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-05","vendors":["unknown"]},"summary":"An attacker with physical access can downgrade the firmware of Yi Home Cameras by inserting a specially crafted SD card, bypassing update security controls.","url":"https://insights.sbomify.com/CVE-2018-3891/"}