# CVE-2017-8230: Privilege escalation in n/a

> Low-privileged users can create admin accounts via HTTP APIs due to missing authorization checks, allowing full device control.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9j3g-g39v-6mhg

## What is CVE-2017-8230?

CVE-2017-8230 is a high-severity vulnerability in n/a, published on 3 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices, the users on the device are divided into 2 groups "admin" and "user". However, as a part of security analysis it was identified that a low privileged user who belongs to the "user" group and who has access to login in to the web administrative interface of the device can add a new administrative user to the interface using HTTP APIs provided by the device and perform all the actions as an administrative user by using that account. 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 functions that performs the various action described in HTTP APIs. If one opens this binary in IDA-pro one will notice that this follows a ARM little endian format. The function at address 0x00429084 in IDA pro is the one that processes the HTTP API request for "addUser" action. If one traces the calls to this function, it can be clearly seen that the function sub_ 41F38C at address 0x0041F588 parses the call received from the browser and passes it to the "addUser" function without any authorization check.

Weakness: CWE-264

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

It affects 1 product.


Products: Amcrest Ipm-721s Firmware.

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

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

## Is CVE-2017-8230 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-13719](https://insights.sbomify.com/CVE-2017-13719/): Memory corruption in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8230 is a high-severity vulnerability in n/a, published on 3 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8230 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-8230/ (Markdown: https://insights.sbomify.com/CVE-2017-8230/index.md)
```

## Sources

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

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