# CVE-2017-20049: Privilege escalation in AXIS OS

> Remote attackers can exploit improper privilege management in legacy Axis camera CGI scripts to escalate privileges.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 15 Jun 2022
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mh3r-vrg4-68p4

## What is CVE-2017-20049?

CVE-2017-20049 is a critical vulnerability in AXIS OS, published on 15 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, was found in legacy Axis devices such as P3225 and M3005. This affects an unknown part of the component CGI Script. The manipulation leads to improper privilege management. It is possible to initiate the attack remotely.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 6 products.


Products: Axis M3005 Firmware, Axis M3007 Firmware, Axis M3045 Firmware, Axis P1204 Firmware, Axis P3225 Firmware, Axis P3367 Firmware.

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

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

## Is CVE-2017-20049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20049 is a critical vulnerability in AXIS OS, published on 15 Jun 2022. 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-20049 in the wild and no public exploit code.

Affected product: AXIS OS. 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-20049/ (Markdown: https://insights.sbomify.com/CVE-2017-20049/index.md)
```

## Sources

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

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