CVE-2024-26015
Fortinet Fortios 7.0.0 – 7.0.15
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:NSummary
CVE-2024-26015 is a low-severity Incorrect Parsing of Numbers with Different Radices (CWE-1389) vulnerability in Fortinet Fortios. Its CVSS base score is 3.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-23311
Vulnerability Data
An incorrect parsing of numbers with different radices vulnerability [CWE-1389] in FortiProxy version 7.4.3 and below, version 7.2.10 and below, version 7.0.17 and below and FortiOS version 7.4.3 and below, version 7.2.8 and below, version 7.0.15 and below IP address…
more
validation feature may permit an unauthenticated attacker to bypass the IP blocklist via crafted requests.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds incorrect type conversions or casts.
Requiring documented development standards and tools can mandate safe typing, casting rules, and compiler checks that stop the weakness from being introduced.
Security engineering principles can require type-safe design and casting practices that structurally avoid incorrect conversions.
Input validation can require numeric fields to be accepted only in explicit, unambiguous formats that handle or reject alternate radices.
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 prevent incorrect numeric parsing by enforcing input-handling standards and code review.
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.
Security testing can detect radix-related parsing flaws but does not prevent them by itself.
Secure development lifecycle requires input validation and parsing rules that would catch radix assumptions.
Application security requirements include explicit handling of numeric input formats and bases.
Secure architecture principles discourage unsafe type conversions in design.
Secure coding standards directly mandate safe numeric parsing and validation of input bases.