CVE-2023-21414: NCC Group has found a flaw during the annual internal penetration test ordered by Axis Communications.
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 16, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-121
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.8
- CNA · Axis
- 7.1
- 0.3 point gap
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| axis | axis os | cpe:2.3:o:axis:axis_os |
| axis | m3215 | cpe:2.3:h:axis:m3215 |
| axis | m3216 | cpe:2.3:h:axis:m3216 |
| axis | m4317-plve | cpe:2.3:h:axis:m4317-plve |
| axis | m4318-plve | cpe:2.3:h:axis:m4318-plve |
| axis | m4327-p | cpe:2.3:h:axis:m4327-p |
| axis | m4328-p | cpe:2.3:h:axis:m4328-p |
| axis | p1467-le | cpe:2.3:h:axis:p1467-le |
| axis | p1468-le | cpe:2.3:h:axis:p1468-le |
| axis | p1468-xle | cpe:2.3:h:axis:p1468-xle |
| axis | p3265-lv | cpe:2.3:h:axis:p3265-lv |
| axis | p3265-lve | cpe:2.3:h:axis:p3265-lve |
and 23 more
Using axis os? Add it to your stack and be the first to know about CVEs like this one. (IP camera)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Axis). Independent of NVD's CPE analysis and usually ahead of it.
Axis Communications AB AXIS A8207-VE Mk II
- AXIS OS 11.5 or earlieraffected
Axis Communications AB AXIS OS
- AXIS OS 10.11 - 11.5affected
Axis Communications AB AXIS Q3527-LVE
- AXIS OS 10.11 - 11.5affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- axis axis os10.11.55 and later · before 10.12.206
- axis axis os11.0.89 and later · before 11.6.94
- axis axis osbefore 11.6.94
Same product
axis: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-1185A configuration file on the local file system had improper input validation which could allow code execution and potentially lead to…35Monitor
- CVE-2025-11142The VAPIX API mediaclip.cgi that did not have a sufficient input validation allowing for a possible remote code execution.35Monitor
- CVE-2025-0358During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Device Configuration…35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-21404May 8, 2023 · AXIS OS 11.0.X - 11.3.x use a static RSA key in legacy LUA-components to protect Axis-specific source code.21Monitor
- ← EarlierCVE-2023-21413Oct 16, 2023 · Remote code execution vulnerability during the installation of ACAP applications on the Axis device28Monitor
- Later →CVE-2023-21415Oct 16, 2023 · Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API overlay_del.cgi is vulnerable to path traversal…32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.