# CVE-2017-8227: Security feature bypass in n/a

> Attackers can bypass account lockout mechanisms on Amcrest IP cameras by using the ONVIF interface to brute force credentials, leading to unauthorized access.

- **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-9j32-qqv8-8pjg

## What is CVE-2017-8227?

CVE-2017-8227 is a critical 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

Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices have a timeout policy to wait for 5 minutes in case 30 incorrect password attempts are detected using the Web and HTTP API interface provided by the device. However, if the same brute force attempt is performed using the ONVIF specification (which is supported by the same binary) then there is no account lockout or timeout executed. This can allow an attacker to circumvent the account protection mechanism and brute force the 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 performs the credential check in the binary for the ONVIF specification. If one opens this binary in IDA-pro one will notice that this follows a ARM little endian format. The function at address 00671618 in IDA pro is parses the WSSE security token header. The sub_ 603D8 then performs the authentication check and if it is incorrect passes to the function sub_59F4C which prints the value "Sender not authorized."

Weakness: CWE-254

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

It affects 1 product.


Products: Amcrest Ipm-721s Firmware.

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

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

## Is CVE-2017-8227 being exploited?

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

What it is: CVE-2017-8227 is a critical 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-8227 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-8227/ (Markdown: https://insights.sbomify.com/CVE-2017-8227/index.md)
```

## Sources

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

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