CVE-2017-8229

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices allow an unauthenticated attacker to download the administrative credentials. 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_436D6 in IDA pro is identified to be setting up the configuration for the device. If one scrolls to the address 0x000437C2 then one can see that /current_config is being set as an ALIAS for /mnt/mtd/Config folder on the device. If one TELNETs into the device and navigates to /mnt/mtd/Config folder, one can observe that it contains various files such as Account1, Account2, SHAACcount1, etc. This means that if one navigates to http://[IPofcamera]/current_config/Sha1Account1 then one should be able to view the content of the files. The security researchers assumed that this was only possible only after authentication to the device. However, when unauthenticated access tests were performed for the same URL as provided above, it was observed that the device file could be downloaded without any authentication.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
78
EG Risk 78/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation74% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
74%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 3, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 7, 2026
No fix on record yet.
generic

Bugtraq: Newly releases IoT security issues

https://seclists.org/bugtraq/2019/Jun/8
generic

IoT_vulnerabilities/Amcrest_sec_issues.pdf at master · ethanhunnt/IoT_vulnerabilities · GitHub

https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Amcrest_sec_issues.pdf
generic

Packet Storm

http://packetstormsecurity.com/files/153224/Amcrest-IPM-721S-Credential-Disclosure-Privilege-Escalation.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:02 UTCEPSS rescore
  2. 2026-10-07 23:41 UTCEPSS rescore
  3. 2026-10-06 15:12 UTCEPSS rescore
  4. 2026-10-03 14:21 UTCEPSS rescore
  5. 2026-10-03 14:21 UTCEPSS rescore
  6. 2026-09-30 09:41 UTCEG score recompute
  7. 2026-09-26 15:53 UTCEPSS rescore
  8. 2026-09-24 13:59 UTCEPSS rescore
  9. 2026-09-23 13:42 UTCEPSS rescore
  10. 2026-09-21 20:27 UTCEPSS rescore
  11. 2026-09-17 19:22 UTCEPSS rescore
  12. 2026-09-17 19:22 UTCEPSS rescore
  13. 2026-09-13 16:42 UTCEPSS rescore
  14. 2026-09-12 14:56 UTCEPSS rescore
  15. 2026-09-11 09:31 UTCEPSS rescore
  16. 2026-09-05 15:24 UTCEPSS rescore
  17. 2026-09-02 14:07 UTCEPSS rescore
  18. 2026-09-02 14:07 UTCEPSS rescore
  19. 2026-08-30 19:13 UTCEPSS rescore
  20. 2026-08-28 21:36 UTCEPSS rescore
  21. 2026-08-26 14:41 UTCEPSS rescore
  22. 2026-08-25 13:44 UTCEPSS rescore
  23. 2026-08-23 00:14 UTCEPSS rescore
  24. 2026-08-21 23:44 UTCEPSS rescore
  25. 2026-08-19 16:59 UTCEPSS rescore
Show 63 more
  1. 2026-08-16 02:10 UTCEPSS rescore
  2. 2026-08-15 01:26 UTCEPSS rescore
  3. 2026-08-12 13:46 UTCEPSS rescore
  4. 2026-08-08 16:32 UTCEPSS rescore
  5. 2026-08-06 13:42 UTCEPSS rescore
  6. 2026-08-06 13:42 UTCEPSS rescore
  7. 2026-08-02 02:23 UTCEPSS rescore
  8. 2026-08-02 02:23 UTCEPSS rescore
  9. 2026-07-30 16:24 UTCEPSS rescore
  10. 2026-07-28 15:32 UTCEPSS rescore
  11. 2026-07-26 14:51 UTCEPSS rescore
  12. 2026-07-26 14:51 UTCEPSS rescore
  13. 2026-07-23 01:30 UTCEG score recompute
  14. 2026-07-22 22:10 UTCEG score recompute
  15. 2026-07-22 14:04 UTCEPSS rescore
  16. 2026-07-21 15:21 UTCEPSS rescore
  17. 2026-07-20 17:04 UTCEPSS rescore
  18. 2026-07-20 17:04 UTCEPSS rescore
  19. 2026-07-19 14:28 UTCEPSS rescore
  20. 2026-07-19 14:28 UTCEPSS rescore
  21. 2026-07-18 10:01 UTCEPSS rescore
  22. 2026-07-16 16:59 UTCEPSS rescore
  23. 2026-07-16 16:59 UTCEPSS rescore
  24. 2026-07-15 16:55 UTCEPSS rescore
  25. 2026-07-15 16:54 UTCEPSS rescore
  26. 2026-07-11 08:24 UTCEPSS rescore
  27. 2026-07-05 02:27 UTCEPSS rescore
  28. 2026-07-02 16:54 UTCEPSS rescore
  29. 2026-07-01 15:03 UTCEPSS rescore
  30. 2026-06-30 23:19 UTCEPSS rescore
  31. 2026-06-30 23:19 UTCEPSS rescore
  32. 2026-06-28 14:04 UTCEPSS rescore
  33. 2026-06-28 04:53 UTCEPSS rescore
  34. 2026-06-28 04:53 UTCEPSS rescore
  35. 2026-06-25 13:47 UTCEPSS rescore
  36. 2026-06-24 14:02 UTCEPSS rescore
  37. 2026-06-24 14:02 UTCEPSS rescore
  38. 2026-06-23 21:30 UTCEPSS rescore
  39. 2026-06-23 21:30 UTCEPSS rescore
  40. 2026-06-21 14:54 UTCEPSS rescore
  41. 2026-06-21 14:54 UTCEPSS rescore
  42. 2026-06-21 01:57 UTCEPSS rescore
  43. 2026-06-21 01:57 UTCEPSS rescore
  44. 2026-06-18 17:50 UTCEPSS rescore
  45. 2026-06-17 17:50 UTCEPSS rescore
  46. 2026-06-15 17:45 UTCEPSS rescore
  47. 2026-06-10 13:19 UTCEPSS rescore
  48. 2026-06-08 14:14 UTCEPSS rescore
  49. 2026-06-08 14:14 UTCEPSS rescore
  50. 2026-06-05 06:08 UTCEPSS rescore
  51. 2026-06-05 06:08 UTCEPSS rescore
  52. 2026-06-01 13:49 UTCEPSS rescore
  53. 2026-06-01 13:49 UTCEPSS rescore
  54. 2026-05-31 00:14 UTCEPSS rescore
  55. 2026-05-31 00:14 UTCEPSS rescore
  56. 2026-05-29 13:41 UTCEPSS rescore
  57. 2026-05-28 13:42 UTCEPSS rescore
  58. 2026-05-28 13:42 UTCEPSS rescore
  59. 2026-05-27 17:43 UTCEG score recompute
  60. 2026-05-27 17:43 UTCGHSA enrichment
  61. 2026-05-27 13:38 UTCEPSS rescore
  62. 2026-05-27 13:38 UTCEPSS rescore
  63. 2026-05-25 06:37 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2017/CVE-2017-8229.yaml
    First seen Jan 1, 2017

    Amcrest IP Camera Web Management - Data Exposure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-8229?
CVE-2017-8229 is a critical vulnerability published on July 3, 2019. Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices allow an unauthenticated attacker to download the administrative credentials. 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…
When was CVE-2017-8229 disclosed?
CVE-2017-8229 was first published on July 3, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8229 actively exploited?
CVE-2017-8229 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-8229?
CVE-2017-8229 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-8229?
No fix for CVE-2017-8229 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-8229

Explore →

Is Your Infrastructure Affected by CVE-2017-8229?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs