# CVE-2017-13719: Memory corruption in n/a

> A stack-based buffer overflow in the HTTP API allows attackers to execute arbitrary code or escalate privileges on Amcrest IP cameras.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xpwc-9c3w-mmc4

## What is CVE-2017-13719?

CVE-2017-13719 is a critical memory corruption 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.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-13719?

It affects 1 product.


Products: Amcrest Ipm-721s Firmware.

## How do I fix CVE-2017-13719?

No fix has been published for CVE-2017-13719 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-13719 being exploited?

There is no known exploitation of CVE-2017-13719 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-8226](https://insights.sbomify.com/CVE-2017-8226/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8227](https://insights.sbomify.com/CVE-2017-8227/): Security feature bypass in n/a (critical 9.8)
- [CVE-2017-8229](https://insights.sbomify.com/CVE-2017-8229/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-8228](https://insights.sbomify.com/CVE-2017-8228/): Missing authorization in n/a (high 8.8)
- [CVE-2017-8230](https://insights.sbomify.com/CVE-2017-8230/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13719 and fix it if it is affected.

What it is: CVE-2017-13719 is a critical memory corruption 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.
Exploitation: There is no known exploitation of CVE-2017-13719 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-13719/ (Markdown: https://insights.sbomify.com/CVE-2017-13719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-13719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-13719
- OSV: https://osv.dev/vulnerability/CVE-2017-13719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-13719/
Summaries are generated and may contain mistakes; the official description above is the record.