# CVE-2020-7222: Auth bypass in n/a

> Attackers can bypass authentication by modifying a JavaScript parameter, gaining read-only access to the Amcrest Web Server interface.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4xwf-xm4x-8cjg

## What is CVE-2020-7222?

CVE-2020-7222 is a medium-severity authentication bypass vulnerability in n/a, published on 17 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Amcrest Web Server 2.520.AC00.18.R 2017-06-29 WEB 3.2.1.453504. The login page responds with JavaScript when one tries to authenticate. An attacker who changes the result parameter (to true) in this JavaScript code can bypass authentication and achieve limited privileges (ability to see every option but not modify them).

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-7222?

It affects 1 product.


Products: Amcrest Web Server.

## How do I fix CVE-2020-7222?

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

## Is CVE-2020-7222 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7222 and fix it if it is affected.

What it is: CVE-2020-7222 is a medium-severity authentication bypass vulnerability in n/a, published on 17 Jan 2020. 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-2020-7222 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-2020-7222/ (Markdown: https://insights.sbomify.com/CVE-2020-7222/index.md)
```

## Sources

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

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