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

> An attacker can block access to the web interface of Axis devices via a race condition in the VAPIX API, requiring a firmware patch.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2025
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-mh24-4g35-88jp

## What is CVE-2024-47262?

CVE-2024-47262 is a medium-severity vulnerability in AXIS OS, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dzmitry Lukyanenka, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API param.cgi was vulnerable to a race condition attack allowing for an attacker to block access to the web interface of the Axis device. Other API endpoints or services not making use of param.cgi are not affected. 
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-1287 (Improper Validation of Specified Type of Input)

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


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

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

## Is CVE-2024-47262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47262 is a medium-severity vulnerability in AXIS OS, published on 4 Mar 2025. 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-2024-47262 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-47262/ (Markdown: https://insights.sbomify.com/CVE-2024-47262/index.md)
```

## Sources

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

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