# CVE-2024-7784: Security feature bypass in AXIS OS

> Attackers can bypass Secure Boot protection in AXIS OS, allowing sophisticated tampering with the device's integrity.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-fmjv-qpc7-997r

## What is CVE-2024-7784?

CVE-2024-7784 is a medium-severity vulnerability in AXIS OS, published on 10 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

During internal Axis Security Development Model (ASDM) threat-modelling, a flaw was found in the protection for device tampering (commonly known as Secure Boot) in AXIS OS making it vulnerable to a sophisticated attack to bypass this protection. To Axis' knowledge, there are no known exploits of the vulnerability at this time. 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-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2024-7784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7784 is a medium-severity vulnerability in AXIS OS, published on 10 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7784 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-7784/ (Markdown: https://insights.sbomify.com/CVE-2024-7784/index.md)
```

## Sources

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

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