{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8226 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8226 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8226 is a critical vulnerability in n/a, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8226 and fix it if it is affected.\n\nWhat it is: CVE-2017-8226 is a critical vulnerability in n/a, published on 3 Jul 2019. 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-2017-8226 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-2017-8226/ (Markdown: https://insights.sbomify.com/CVE-2017-8226/index.md)","id":"CVE-2017-8226","markdown":"https://insights.sbomify.com/CVE-2017-8226/index.md","name":"CVE-2017-8226","record":{"aliases":["GHSA-g3mq-ffvf-8f3r"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Amcrest IP camera","requires_auth":"none","summary":"Attackers can extract hardcoded default credentials from Amcrest IP camera firmware to gain unauthorized access to the device.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ipm-721s_firmware","vendor":"amcrest"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices have default credentials that are hardcoded in the firmware and can be extracted by anyone who reverses the firmware to identify them. If the firmware version V2.420.AC00.16.R 9/9/2016 is dissected using binwalk tool, one obtains a _user-x.squashfs.img.extracted archive which contains the filesystem set up on the device that many of the binaries in the /usr folder. The binary \"sonia\" is the one that has the vulnerable function that sets up the default credentials on the device. If one opens this binary in IDA-pro, one will notice that this follows a ARM little endian format. The function sub_3DB2FC in IDA pro is identified to be setting up the values at address 0x003DB5A6. The sub_5C057C then sets this value and adds it to the Configuration files in /mnt/mtd/Config/Account1 file.","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-2017-8226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2017-8227"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2017-8225"},"products":["n/a"],"published":"2019-07-03","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-13719","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-8227","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2017-8229","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2017-8228","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-8230","kev_date_added":null,"published":"2019-07-03"}],"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":"Attackers can extract hardcoded default credentials from Amcrest IP camera firmware to gain unauthorized access to the device.","url":"https://insights.sbomify.com/CVE-2017-8226/"}