dbcve.org
Axis OsOperating system · Axis

CVE-2023-21414

MEDIUM · 6.8 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to 10.12.206 / 11.6.94 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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
NCC Group has found a flaw during the annual internal penetration test ordered by Axis Communications. The protection for device tampering (commonly known as Secure Boot) contains a flaw which provides an opportunity for a sophisticated attack to bypass this protection. 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

This is a Secure Boot bypass vulnerability in Axis Communications devices running AXIS OS. During a penetration test, NCC Group discovered a flaw that allows a sophisticated attacker to circumvent the device tampering protection mechanism. Axis has released patched AXIS OS versions to address this vulnerability.

MitigationApply the patched AXIS OS versions released by Axis Communications. Organizations should review the Axis security advisory to identify affected devices and apply updates in accordance with their patch management processes.

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.11.55, < 10.12.206>= 11.0.89, < 11.6.94< 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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/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. Confirm Axis device and OS type
    Identify that the device is an Axis Communications product running AXIS OS firmware. This can be done via the device web interface under System > About, or via CLI command 'show version' or 'version'.
    Affected if The device is not an Axis device running AXIS OS.
  2. Retrieve installed AXIS OS version
    Access the device web interface and navigate to System > About > AXIS OS, or use the CLI command 'show version' to obtain the exact firmware version number.
    Affected if Unable to retrieve the version number.
  3. Compare version against vulnerable ranges
    Compare your installed AXIS OS version to the following vulnerable ranges: 10.11.55 through 10.12.205, or 11.0.89 through 11.6.93. Versions below 10.12.206 and below 11.6.94 are affected.
    Affected if The installed version falls within 10.11.55 <= version < 10.12.206 OR 11.0.89 <= version < 11.6.94.

A user is affected if their Axis device runs AXIS OS version 10.11.55 or higher but below 10.12.206, or version 11.0.89 or higher but below 11.6.94.

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.206 / 11.6.94 or later
Fixed in 10.12.20611.6.94
Interim mitigation

Apply the patched AXIS OS versions released by Axis Communications. Organizations should review the Axis security advisory to identify affected devices and apply updates in accordance with their patch management processes.

Recommended fix High confidence

AXIS OS 10.12.206 or later, or AXIS OS 11.6.94 or later (depending on target version branch)

  1. Identify the current AXIS OS version running on the device via the web interface or CLI
  2. Determine which version branch is currently in use (10.x or 11.x)
  3. For devices running AXIS OS 10.11.55 or later but earlier than 10.12.206: upgrade to AXIS OS version 10.12.206 or later
  4. For devices running AXIS OS 11.0.89 or later but earlier than 11.6.94: upgrade to AXIS OS version 11.6.94 or later
  5. For devices running any version earlier than 11.6.94: upgrade to AXIS OS version 11.6.94 or later
  6. Download the appropriate firmware from the official Axis download portal at www.axis.com/support/downloads
  7. Upload and install the new firmware via the device web interface or Axis Device Manager
  8. Verify the upgrade was successful and the device is functioning normally
Caveat Review Axis release notes for the target version for any feature changes or migration considerations before upgrading

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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