{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-19071 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19071 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19071 is a high-severity vulnerability in n/a, published on 7 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-19071 and fix it if it is affected.\n\nWhat it is: CVE-2018-19071 is a high-severity vulnerability in n/a, published on 7 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-19071 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-2018-19071/ (Markdown: https://insights.sbomify.com/CVE-2018-19071/index.md)","id":"CVE-2018-19071","markdown":"https://insights.sbomify.com/CVE-2018-19071/index.md","name":"CVE-2018-19071","record":{"aliases":["GHSA-5fxp-6x34-j5xh"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Foscam IP camera","requires_auth":"low_privilege","summary":"Local attackers can modify the boot script due to insecure permissions, allowing arbitrary command execution with root privileges at system startup.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"c2_application_firmware","vendor":"foscam"},{"product":"c2_system_firmware","vendor":"foscam"},{"product":"i5_application_firmware","vendor":"opticam"},{"product":"i5_system_firmware","vendor":"opticam"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"An issue was discovered on Foscam C2 devices with System Firmware 1.11.1.8 and Application Firmware 2.72.1.32, and Opticam i5 devices with System Firmware 1.5.2.11 and Application Firmware 2.21.1.128. /mnt/mtd/boot.sh has 0777 permissions, allowing local users to control the commands executed at system start-up.","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":"Misconfiguration in n/a","id":"CVE-2018-19071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2018-19072"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-19070"},"products":["n/a"],"published":"2018-11-07","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-19063","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-19064","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-19067","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-19069","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-19076","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-19078","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-19081","kev_date_added":null,"published":"2018-11-07"}],"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-05","vendors":["n/a"]},"summary":"Local attackers can modify the boot script due to insecure permissions, allowing arbitrary command execution with root privileges at system startup.","url":"https://insights.sbomify.com/CVE-2018-19071/"}