CVE-2023-21404
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 · uneditedAXIS OS 11.0.X - 11.3.x use a static RSA key in legacy LUA-components to protect Axis-specific source code. The static RSA key is not used in any other secure communication nor can it be used to compromise the device or any customer data.
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 confidenceAXIS OS versions 11.0.X through 11.3.x contain a static RSA key embedded in legacy LUA components, used to protect Axis-specific source code. While the use of a static cryptographic key is generally insecure, the vendor explicitly states this key is not used in any other secure communications and cannot be exploited to compromise the device or access customer data.
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>= 11.0.89, < 11.4.52CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the device is an Axis productIdentify the device manufacturer through network discovery, device web interface, or physical labeling. This CVE applies only to Axis devices running AXIS OS.Affected if The device is not manufactured by Axis
-
Determine the installed AXIS OS versionAccess the device web interface and navigate to the System > About page, or use the Axis API/CLI command 'gzip -dc /proc/sys/urlid' or check the banner via FTP/telnet connection. Alternatively, query the device remotely using ONVIF or Axis discovery protocol.Affected if Unable to retrieve the AXIS OS version
-
Compare your version against the affected rangeCheck the AXIS OS version number against the vulnerable range: versions 11.0.89 through 11.3.x (anything >= 11.0.89 but < 11.4.52).Affected if The installed version falls within >= 11.0.89 and < 11.4.52
You are affected if you are running AXIS OS on an Axis device and the installed version is 11.0.89 or higher but below 11.4.52.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.4.52
Upgrade AXIS OS to a version beyond 11.3.x when patches become available. As the vulnerability has limited scope per the vendor, prioritize based on overall device security posture and existing update schedules.
Axis OS 11.4.52 or later
- 1. Identify all Axis devices running affected Axis OS versions (11.0.89 through 11.4.51)
- 2. Review the device inventory and determine which devices have legacy LUA-components that may use the static RSA key
- 3. Plan maintenance window for upgrade procedure
- 4. Download Axis OS version 11.4.52 or later from the official Axis website
- 5. Upload the new firmware to each affected device via Axis Device Manager or the device web interface
- 6. Verify successful upgrade and confirm the new version is running
- 7. After upgrade, verify that legacy LUA-components are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-21404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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