# CVE-2017-8228: Missing authorization in n/a

> Attackers can hijack unclaimed or recently rebooted Amcrest cameras by knowing the serial number, gaining full control to view video and modify settings.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jhmv-phvh-7v48

## What is CVE-2017-8228?

CVE-2017-8228 is a high-severity missing authorization vulnerability in n/a, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices mishandle reboots within the past two hours. Amcrest cloud services does not perform a thorough verification when allowing the user to add a new camera to the user's account to ensure that the user actually owns the camera other than knowing the serial number of the camera. This can allow an attacker who knows the serial number to easily add another user's camera to an attacker's cloud account and control it completely. This is possible in case of any camera that is currently not a part of an Amcrest cloud account or has been removed from the user's cloud account. Also, another requirement for a successful attack is that the user should have rebooted the camera in the last two hours. However, both of these conditions are very likely for new cameras that are sold over the Internet at many ecommerce websites or vendors that sell the Amcrest products. The successful attack results in an attacker being able to completely control the camera which includes being able to view and listen on what the camera can see, being able to change the motion detection settings and also be able to turn the camera off without the user being aware of it. Note: The same attack can be executed using the Amcrest Cloud mobile application.

Weakness: CWE-264

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

It affects 1 product.


Products: Amcrest Ipm-721s Firmware.

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

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

## Is CVE-2017-8228 being exploited?

There is no known exploitation of CVE-2017-8228 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-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-8228 and fix it if it is affected.

What it is: CVE-2017-8228 is a high-severity missing authorization vulnerability in n/a, published on 3 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8228 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-8228/ (Markdown: https://insights.sbomify.com/CVE-2017-8228/index.md)
```

## Sources

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

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