# CVE-2024-47260: Denial of service in AXIS OS

> Insufficient input validation in the VAPIX API allows attackers to exhaust device memory by uploading excessive audio clips, causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 4 Mar 2025
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-q68r-x3xx-f2m3

## What is CVE-2024-47260?

CVE-2024-47260 is a medium-severity denial of service vulnerability in AXIS OS, published on 4 Mar 2025. 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 mediaclip.cgi did not have a sufficient input validation allowing for uploading more audio clips then designed resulting in the Axis device running out of memory. 
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-641 (Improper Restriction of Names for Files and Other Resources)

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


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

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

## Is CVE-2024-47260 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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