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

> An attacker can block access to the guard tour configuration page in the web interface of Axis devices by exploiting an API parameter validation flaw.

- **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:** 10 Sep 2024
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-288p-75q5-6gj7

## What is CVE-2024-6173?

CVE-2024-6173 is a medium-severity denial of service vulnerability in AXIS OS, published on 10 Sep 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 a Guard Tour VAPIX API parameter allowed the use of arbitrary values allowing for an attacker to block access to the guard tour configuration page in the web interface of the Axis device. 
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-6173?


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

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

## Is CVE-2024-6173 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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