# CVE-2024-8772: Race condition in AXIS OS

> Authenticated attackers can exploit a race condition in the VAPIX API to block access to the overlay configuration page on Axis devices.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 26 Nov 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-3v44-23hf-q5wp

## What is CVE-2024-8772?

CVE-2024-8772 is a medium-severity vulnerability in AXIS OS, published on 26 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

51l3nc3, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API managedoverlayimages.cgi was vulnerable to a race condition attack allowing for an attacker to block access to the overlay configuration page in the web interface of the Axis device. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

Weakness: CWE-1286 (Improper Validation of Syntactic Correctness of Input)

## Which versions are affected by CVE-2024-8772?


## How do I fix CVE-2024-8772?

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

## Is CVE-2024-8772 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8772 and fix it if it is affected.

What it is: CVE-2024-8772 is a medium-severity vulnerability in AXIS OS, published on 26 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8772 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-2024-8772/ (Markdown: https://insights.sbomify.com/CVE-2024-8772/index.md)
```

## Sources

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

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