dbcve.org
Axis OsOperating system · Axis

CVE-2023-21413

HIGH · 7.2 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to 10.12.199 / 11.6.94 or later.
See remediation →
78/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
GoSecure on behalf of Genetec Inc. has found a flaw that allows for a remote code execution during the installation of ACAP applications on the Axis device. The application handling service in AXIS OS was vulnerable to command injection allowing an attacker to run arbitrary code. 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

Command injection vulnerability in the AXIS OS application handling service allows remote attackers to execute arbitrary code during the installation of ACAP (Axis Application) applications on affected Axis devices.

MitigationApply the patched AXIS OS versions released by Axis as detailed in the official Axis security advisory to remediate the command injection vulnerability.

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:>= 10.5.0, < 10.12.199>= 11.0.89, < 11.6.94

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 installed AXIS OS version
    Access the device web interface under System > About or use the command 'axsysinfo' via SSH/CLI to retrieve the current firmware version
    Affected if The version falls within 10.5.0-10.12.198 or 11.0.89-11.6.93
  2. Verify ACAP application functionality is accessible
    Log into the device web interface and navigate to Apps or check if the ACAP application management interface is reachable via the API at /axis-cgi/applications/list.cgi
    Affected if The ACAP application management interface is accessible and functional on the device
  3. Confirm application handling service is active
    Check device processes via SSH using 'ps | grep -i acap' or inspect the application handling daemon status through the device's system log
    Affected if The ACAP application handling service is running and accepting installation requests

A user is affected if their AXIS device runs a version between 10.5.0-10.12.198 or 11.0.89-11.6.93 AND has the ACAP application handling service enabled and accessible.

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 10.12.199 / 11.6.94 or later
Fixed in 10.12.19911.6.94
Interim mitigation

Apply the patched AXIS OS versions released by Axis as detailed in the official Axis security advisory to remediate the command injection vulnerability.

Recommended fix High confidence

AXIS OS 10.12.199 or later (10.x branch); AXIS OS 11.6.94 or later (11.x branch)

  1. 1. Identify the current AXIS OS version running on the affected device via the device web interface or AXIS Device Manager
  2. 2. If running a version >= 10.5.0 and < 10.12.199, plan upgrade to version 10.12.199 or later in the 10.x branch
  3. 3. If running a version >= 11.0.89 and < 11.6.94, plan upgrade to version 11.6.94 or later in the 11.x branch
  4. 4. Download the appropriate AXIS OS upgrade from the Axis website or your designated software distribution channel
  5. 5. Apply the upgrade through the device web interface (System > Maintenance > AXIS OS upgrade) or via AXIS Device Manager
  6. 6. Verify the upgrade was successful by confirming the new firmware version matches the intended patched release
  7. 7. After upgrade, test ACAP application installation functionality to ensure the vulnerability is resolved and normal operations function correctly

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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