dbcve.org
Axis OsOperating system · Axis

CVE-2024-47259

HIGH · 7.1 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 11.11.126 / 12.2.52 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Girishunawane, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API dynamicoverlay.cgi did not have a sufficient input validation allowing for a possible command injection leading to being able to transfer files to the Axis device with the purpose to exhaust system resources. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the AXIS VAPIX API dynamicoverlay.cgi endpoint due to insufficient input validation. An attacker can inject arbitrary commands through this CGI interface, enabling file transfers to the device to exhaust system resources (denial of service). The vulnerability has a CVSS score of 7.1 (HIGH).

MitigationApply the vendor-released patched AXIS OS versions to all affected Axis devices. Identify all devices running vulnerable AXIS OS versions through network inventory, update firmware to patched versions, and verify remediation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Axis OsOperating system
Affected:>= 11.11.0, < 12.2.52
Axis Os 2024Operating system
Affected:< 11.11.126

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed AXIS OS version
    Query the device through its web interface under System > About or use the VAPIX API 'param.cgi?action=upgradeinfo' endpoint to retrieve the firmware version
    Affected if The installed version is 11.11.0 or higher but below 12.2.52, or below 11.11.126 for the 2024 release branch
  2. Confirm VAPIX API service is running
    Verify the VAPIX API service is enabled on the device by checking the network services configuration in the device web interface under Network > TCP/IP > Advanced or by attempting a basic VAPIX request to the device
    Affected if VAPIX API is accessible on the device (typically ports 80 or 443)
  3. Check if dynamicoverlay.cgi is accessible
    Send a request to the /vapix/dynamicoverlay.cgi endpoint (e.g., curl http://DEVICE_IP/vapix/dynamicoverlay.cgi) and observe if it responds
    Affected if The endpoint responds with any output, indicating it is exposed

A device is affected if it runs a vulnerable AXIS OS version (11.11.0 to 12.2.52 or 2024 branch below 11.11.126) AND has the VAPIX API with the dynamicoverlay.cgi endpoint accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.11.126 / 12.2.52 or later
Fixed in 11.11.12612.2.52
Interim mitigation

Apply the vendor-released patched AXIS OS versions to all affected Axis devices. Identify all devices running vulnerable AXIS OS versions through network inventory, update firmware to patched versions, and verify remediation.

Recommended fix High confidence

AXIS OS 12.2.52 or later, or AXIS OS 2024 11.11.126 or later

  1. Identify the current AXIS OS version running on the device through the web interface or VAPIX API
  2. Determine which release train your device is on (AXIS OS or AXIS OS 2024) based on your current version
  3. Access the Axis support portal or download center at www.axis.com to obtain the latest patched version
  4. For AXIS OS devices: upgrade to version 12.2.52 or later
  5. For AXIS OS 2024 devices: upgrade to version 11.11.126 or later
  6. Follow Axis standard upgrade procedures (via web interface or VAPIX firmware upgrade API) to apply the update
  7. Verify the upgrade was successful and the device is running a patched version
Caveat Standard AXIS OS upgrade considerations apply - review release notes for your specific device model for any compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axis Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47259 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data