CVE-2017-13719

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2019 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

The Amcrest IPM-721S Amcrest_IPC-AWXX_Eng_N_V2.420.AC00.17.R.20170322 allows HTTP requests that permit enabling various functionalities of the camera by using HTTP APIs, instead of the web management interface that is provided by the application. This HTTP API receives the credentials as base64 encoded in the Authorization HTTP header. However, a missing length check in the code allows an attacker to send a string of 1024 characters in the password field, and allows an attacker to exploit a memory corruption issue. This can allow an attacker to circumvent the account protection mechanism and brute force the credentials. If the firmware version Amcrest_IPC-AWXX_Eng_N_V2.420.AC00.17.R.20170322 is dissected using the binwalk tool, one obtains a _user-x.squashfs.img.extracted archive which contains the filesystem set up on the device that has many of the binaries in the /usr folder. The binary "sonia" is the one that has the vulnerable function that performs the credential check in the binary for the HTTP API specification. If we open this binary in IDA Pro we will notice that this follows an ARM little-endian format. The function at address 00415364 in IDA Pro starts the HTTP authentication process. This function calls another function at sub_ 0042CCA0 at address 0041549C. This function performs a strchr operation after base64 decoding the credentials, and stores the result on the stack, which results in a stack-based buffer overflow.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
46
EG Risk 46/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation4.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2019. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
4.5%
EPSS %ILE
91st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2019. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 3, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 7, 2026
No fix on record since 2019.
Web page

Bugtraq: Newly releases IoT security issues

https://seclists.org/bugtraq/2019/Jun/8
Web page

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

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

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 12× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 137 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 00:30 UTCEG score recompute
  2. 2026-10-14 00:30 UTCGHSA enrichmentGHSA-xpwc-9c3w-mmc4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:27 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  4. 2026-10-12 20:35 UTCGHSA enrichmentGHSA-xpwc-9c3w-mmc4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-12 20:34 UTCEG score recompute
  6. 2026-10-12 16:28 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  7. 2026-10-12 00:58 UTCEG score recompute
  8. 2026-10-11 13:40 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  9. 2026-10-10 19:55 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  10. 2026-10-09 20:02 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  11. 2026-10-08 16:35 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  12. 2026-10-07 23:41 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  13. 2026-10-06 15:11 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  14. 2026-10-05 17:38 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  15. 2026-10-04 23:18 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  16. 2026-10-03 14:21 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  17. 2026-09-30 14:58 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  18. 2026-09-30 09:26 UTCEG score recompute
  19. 2026-09-28 13:45 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  20. 2026-09-27 13:40 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  21. 2026-09-26 15:53 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  22. 2026-09-24 13:59 UTCEPSS rescoreEPSS 4.5% · 91st percentile
  23. 2026-09-19 15:36 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  24. 2026-09-18 19:22 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  25. 2026-09-17 19:22 UTCEPSS rescoreEPSS 4.5% · 90th percentile
Show 67 more
  1. 2026-09-15 03:05 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  2. 2026-09-12 14:55 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  3. 2026-09-11 09:31 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  4. 2026-09-10 09:26 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  5. 2026-09-07 15:56 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  6. 2026-09-04 13:56 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  7. 2026-09-04 05:01 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  8. 2026-09-02 14:07 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  9. 2026-09-01 13:48 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  10. 2026-09-01 03:31 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  11. 2026-08-30 19:13 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  12. 2026-08-28 21:36 UTCEPSS rescoreEPSS 3.4% · 87th percentile
  13. 2026-08-27 14:20 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  14. 2026-08-26 14:41 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  15. 2026-08-25 13:44 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  16. 2026-08-24 14:10 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  17. 2026-08-21 23:44 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  18. 2026-08-20 22:50 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  19. 2026-08-19 16:59 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  20. 2026-08-18 13:43 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  21. 2026-08-17 13:42 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  22. 2026-08-16 14:51 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  23. 2026-08-16 02:10 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  24. 2026-08-15 01:26 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  25. 2026-08-13 21:56 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  26. 2026-08-09 13:42 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  27. 2026-08-08 16:32 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  28. 2026-08-07 16:22 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  29. 2026-08-06 13:42 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  30. 2026-08-05 19:12 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  31. 2026-08-04 15:05 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  32. 2026-08-04 10:32 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  33. 2026-08-03 10:30 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  34. 2026-08-02 02:23 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  35. 2026-08-01 04:11 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  36. 2026-07-30 16:24 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  37. 2026-07-30 01:26 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  38. 2026-07-28 15:32 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  39. 2026-07-25 14:13 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  40. 2026-07-23 14:15 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  41. 2026-07-23 01:27 UTCEG score recompute
  42. 2026-07-22 22:06 UTCEG score recompute
  43. 2026-07-22 14:04 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  44. 2026-07-21 15:21 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  45. 2026-07-20 17:04 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  46. 2026-07-19 14:28 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  47. 2026-07-19 02:26 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  48. 2026-07-18 10:00 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  49. 2026-07-16 16:59 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  50. 2026-07-15 16:54 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  51. 2026-07-15 01:56 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  52. 2026-07-13 22:26 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  53. 2026-07-13 06:09 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  54. 2026-07-12 05:43 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  55. 2026-07-11 08:24 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  56. 2026-07-09 19:06 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  57. 2026-07-08 15:10 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  58. 2026-07-07 13:42 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  59. 2026-07-06 16:24 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  60. 2026-07-06 02:20 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  61. 2026-07-05 02:27 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  62. 2026-07-04 06:28 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  63. 2026-07-01 15:02 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  64. 2026-06-30 23:19 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  65. 2026-06-29 14:03 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  66. 2026-06-28 04:53 UTCEPSS rescoreEPSS 4.5% · 90th percentile
  67. 2026-06-27 03:05 UTCEPSS rescoreEPSS 4.5% · 90th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-13719?
CVE-2017-13719 is a critical-severity vulnerability; its CVE record was published on July 3, 2019. The Amcrest IPM-721S AmcrestIPC-AWXXEngNV2.420.AC00.17.R.20170322 allows HTTP requests that permit enabling various functionalities of the camera by using HTTP APIs, instead of the web management interface that is provided by the application. This HTTP API receives the credentials as base64 encoded…
When was CVE-2017-13719 made public?
CVE-2017-13719 was made public on June 7, 2019: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 3, 2019. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2017-13719 actively exploited?
CVE-2017-13719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.5% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-13719?
CVE-2017-13719 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-13719?
No fix for CVE-2017-13719 has been recorded since its CVE record was published in 2019. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-13719?

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

Book a Demo →Browse All CVEs