CVE-2024-47259
Axis Os 11.11.0 – 12.2.52
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:NSummary
CVE-2024-47259 is a low-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Axis Axis Os. Its CVSS base score is 3.5 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-47259 is a vulnerability in the VAPIX API's dynamicoverlay.cgi component of AXIS OS, stemming from insufficient input validation that enables command injection. This flaw allows attackers to transfer files to affected Axis devices, potentially exhausting system resources. The issue was identified by Girishunawane through the AXIS OS Bug Bounty Program and carries a CVSS v3.1 base score of 3.5 (AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N), mapped to CWE-434 (Unrestricted Upload of File with Dangerous Type).
Exploitation requires network access, high attack complexity, and low privileges (PR:L), with no user interaction needed but a changed scope (S:C). A successful attack enables limited integrity impact (I:L), such as uploading files via command injection to deplete resources on the device, though it does not affect confidentiality or availability per the CVSS vector.
Axis has released patched versions of AXIS OS to address this flaw. For detailed mitigation steps and affected products, refer to the official Axis security advisory at https://www.axis.com/dam/public/13/cd/4a/cve-2024-47259pdf-en-US-466882.pdf.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-54215
Vulnerability Data
Girishunawane, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API dynamicoverlay.cgi did not have a sufficient input validation allowing for a possible command injection leading to being able to transfer files to the Axis device…
more
with the purpose to exhaust system resources. 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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.
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.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
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.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.