dbcve.org
Axis OsOperating system · Axis

CVE-2023-5553

MEDIUM · 6.8 CVSS v3.1 Published 2023-11-21
Fix available
A fix is available. Upgrade to 10.12.213 / 11.7.57 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
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.

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 vulnerability in AXIS OS allows bypass of the Secure Boot protection mechanism, which is designed to prevent device tampering. The flaw was discovered during internal threat-modelling and represents a sophisticated attack vector against the device's firmware integrity controls.

MitigationUpdate affected Axis devices to the patched AXIS OS versions as specified in the Axis security advisory. Given the Secure Boot bypass nature, ensure firmware integrity verification procedures are followed post-update.

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.8, < 11.7.57
Axis Os 2022Operating system
Affected:< 10.12.213

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. Identify installed AXIS OS version
    Access the device web interface and navigate to the System Overview or Status page to view the firmware version. Alternatively, log into the device CLI and run the appropriate version display command.
    Affected if The displayed version is >= 10.8 and < 11.7.57, OR the version belongs to the 2022 branch and is < 10.12.213
  2. Confirm AXIS OS 2022 branch
    If the version number starts with 10.12 or lower, verify it is part of the 2022 release branch by checking the full version string in the device interface or release notes.
    Affected if The installed version is a 2022 branch release and is < 10.12.213
  3. Verify Secure Boot status
    Navigate to the device security settings in the web interface (typically under System > Security or similar) or use the CLI to check Secure Boot configuration status.
    Affected if Secure Boot is enabled and the device is running an affected AXIS OS version from the ranges identified in step 1

The device is affected if it runs AXIS OS version >= 10.8 and < 11.7.57 (or < 10.12.213 for the 2022 branch) AND has Secure Boot protection mechanism enabled.

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.213 / 11.7.57 or later
Fixed in 10.12.21311.7.57
Interim mitigation

Update affected Axis devices to the patched AXIS OS versions as specified in the Axis security advisory. Given the Secure Boot bypass nature, ensure firmware integrity verification procedures are followed post-update.

Recommended fix Moderate confidence

AXIS OS 11.7.57 or AXIS OS 10.12.213 (depending on product model and version branch)

  1. Identify the current AXIS OS version running on the device
  2. Determine which version branch is in use (10.x or 11.x)
  3. Access the Axis device management interface or use Axis Device Manager
  4. Download the appropriate fixed AXIS OS version (11.7.57 or later for current branch, 10.12.213 or later for 2022 branch)
  5. Follow standard Axis firmware upgrade procedure via web interface or AXIS Device Manager
  6. Verify the upgrade was successful and the device is functioning normally
  7. Confirm the new OS version matches the patched release

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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