# CVE-2024-0066: Information disclosure in AXIS OS

> Attackers can intercept sensitive traffic between Axis devices and O3C servers if the O3C feature is enabled, exposing data to eavesdroppers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2024
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-j629-whpq-gxc5

## What is CVE-2024-0066?

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

### Official description

Johan Fagerström, member of the AXIS OS Bug Bounty Program, has found that a O3C feature may expose sensitive traffic between the client (Axis device) and (O3C) server. If O3C is not being used this flaw does not apply. 
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-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2024-0066 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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