CVE-2024-0054
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-0054 is a medium-severity Improper Neutralization of Wildcards or Matching Symbols (CWE-155) vulnerability in Axis OS (inferred from references). Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 46th 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-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-15857
Vulnerability Data
Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX APIs local_list.cgi, create_overlay.cgi and irissetup.cgi was vulnerable for file globbing which could lead to a resource exhaustion attack. Axis has released patched AXIS OS versions…
more
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
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires checking and sanitizing special elements such as wildcards before they are passed downstream.
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.
Secure SDLC practices directly require input neutralization to block wildcard injection.
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.
Secure development lifecycle mandates input validation and sanitization that directly prevents wildcard injection.
A.8.26 requires identifying and specifying requirements (incl. resilience against SQL injections, input validation, and output controls) that can address wildcard neutralization when derived from risk assessment, but does not mandate or enforce their correct implementation in code.
A.8.27 mandates security-by-design principles (including data validation/sanitization, distrust external input, least privilege, defense-in-depth) that reach wildcard neutralization when applied to input flows, but the clause only requires establishing/reviewing/applying the principles and does not itself enforce their correct implementation in every relevant code path or downstream component.
Secure coding standards explicitly require proper escaping or neutralization of wildcard and matching symbols.