Cyber Resilience

CVE-2023-21415

Path Traversal in Axis Os 6.50.5.3 – 6.50.5.14

Published
16 October 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0059 45th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2023-21415 is a medium-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Axis Axis Os. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API overlay_del.cgi is vulnerable to path traversal attacks that allows for file deletion. This flaw can only be exploited after authenticating with an operator- or…

more

administrator-privileged service account. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-21418Same product: Axis Axis Os
CVE-2023-21417Same product: Axis Axis Os
CVE-2025-12757Same vendor: Axis
CVE-2024-0067Shared CWE-22, CWE-35
CVE-2024-2654Shared CWE-22, CWE-35
CVE-2025-41736Shared CWE-22, CWE-35
CVE-2025-40573Shared CWE-22, CWE-35
CVE-2024-49770Shared CWE-22, CWE-35
CVE-2023-5885Shared CWE-22, CWE-35
CVE-2025-26935Shared CWE-22, CWE-35

Affected Assets

axis
axis os
6.50.5.3 — 6.50.5.14 · 11.0.81 — 11.6.94
axis
axis os 2016
6.50.2 — 6.50.5.2
axis
axis os 2018
≤ 8.40.35
axis
axis os 2020
≤ 9.80.47
axis
axis os 2022
≤ 10.12.206

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that neutralize traversal sequences.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect path-traversal flaws before release.

prevents

Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.

prevents

Application security requirements include rules for safe file-path construction and canonicalization.

prevents

Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.

prevents

Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.

mitigates

Information access restriction limits file reachability but does not address the input-validation flaw itself.

References