dbcve.org
Axis OsOperating system · Axis

CVE-2025-0359

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 11.11.135 / 12.2.52 or later.
See remediation →
57/100
Remediation priority · Elevated
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
During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the ACAP Application framework that allowed applications to access restricted D-Bus methods within the framework. 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 · moderate confidence

A flaw in the Axis ACAP Application framework allowed applications to bypass access controls and invoke restricted D-Bus methods. This represents a privilege escalation vulnerability within the application's sandbox environment, potentially allowing malicious or compromised ACAP applications to interact with system services that should be protected.

MitigationApply the patched AXIS OS versions released by Axis Communication to affected devices. Organizations should identify all Axis devices running vulnerable ACAP framework versions and schedule firmware updates following vendor guidance.

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.135

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify the Axis OS version
    Access the device web interface under Settings > System > About, or run 'show version' via CLI/SSH
    Affected if The displayed version falls within 11.11.0 to 12.2.51 (standard Axis OS) or is below 11.11.135 (Axis OS 2024 branch)
  2. Confirm ACAP application support is enabled
    Check the device web interface under Settings > Apps, or query the device for installed ACAP applications via CLI using 'acap list' or similar ACAP management commands
    Affected if One or more ACAP applications are installed or the ACAP framework is active on the device
  3. Verify the D-Bus service configuration
    Inspect the device's D-Bus configuration files in /etc/dbus-1/system.d/ or use dbus-send to examine available system bus services accessible to ACAP applications
    Affected if Restricted D-Bus methods related to system services are exposed to the ACAP application sandbox without proper access controls

The device is affected if it runs a vulnerable Axis OS version (11.11.0 to 12.2.51 or below 11.11.135 on the 2024 branch) and has ACAP applications enabled, allowing potential bypass of D-Bus access controls within the application sandbox.

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.135 / 12.2.52 or later
Fixed in 11.11.13512.2.52
Interim mitigation

Apply the patched AXIS OS versions released by Axis Communication to affected devices. Organizations should identify all Axis devices running vulnerable ACAP framework versions and schedule firmware updates following vendor guidance.

Recommended fix High confidence

Axis OS 12.2.52 or later (or Axis OS 2024 11.11.135 or later for the 2024 branch)

  1. 1. Identify the current Axis OS version running on the device using the device web interface or Axis Device Manager
  2. 2. Determine which Axis OS release branch is in use (main release or 2024 release)
  3. 3. For devices running Axis OS 12.x (versions >= 11.11.0 and < 12.2.52): upgrade to Axis OS version 12.2.52 or later
  4. 4. For devices running Axis OS 2024 branch (versions < 11.11.135): upgrade to Axis OS version 11.11.135 or later
  5. 5. Upgrade via the device web interface under System > Maintenance > Axis OS, or use Axis Device Manager for批量升级
  6. 6. After upgrade, verify the new Axis OS version is >= 12.2.52 (for 12.x branch) or >= 11.11.135 (for 2024 branch)
Caveat Standard Axis OS upgrade - review release notes for any application compatibility changes

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0359 — 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-2025-0359 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