Security Resilience

CVE-2023-40718

Fortinet Fortios Ips Engine ≤ 7.312

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

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-40718 is a high-severity Interpretation Conflict (CWE-436) vulnerability in Fortinet Fortios Ips Engine. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 44th 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

A interpretation conflict in Fortinet IPS Engine versions 7.321, 7.166 and 6.158 allows attacker to evade IPS features via crafted TCP packets.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-36555Same product: Fortinet Fortios
CVE-2024-46665Same product: Fortinet Fortios
CVE-2025-25252Same product: Fortinet Fortios
CVE-2025-64157Same product: Fortinet Fortios
CVE-2025-58325Same product: Fortinet Fortios
CVE-2025-53844Same product: Fortinet Fortios
CVE-2023-42785Same product: Fortinet Fortios
CVE-2023-41841Same product: Fortinet Fortios
CVE-2024-32122Same product: Fortinet Fortios
CVE-2024-36504Same product: Fortinet Fortios

Affected Assets

fortinet
fortios ips engine
≤ 7.312 · ≤ 7.165 · ≤ 6.158

Mitigating Controls

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.

blocks

A.8.25 mandates a secure SDLC process with checkpoints, secure coding, testing and training; it does not stop differing interpretations of shared state or inputs between two products from arising or being exploited

blocks

A.8.26 only requires that security requirements (including resilience against injections or input controls) be identified and specified during development or acquisition; it does not itself enforce, implement or assure any mechanism that stops an interpretation conflict from being exploitable.

blocks

A.8.27 establishes and applies secure-by-design principles (defense-in-depth, least privilege, assume-breach, distrust-external-input, hardening, etc.) but does not stop two products from interpreting the same input or protocol step differently; the resulting state/conflict weakness can still be present and exploitable.

prevents

Secure coding standards can enforce canonical input handling and strict protocol compliance to avoid misinterpretation between products.

finds

Security testing can detect and correct cases where one component misinterprets another’s state or messages.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-436, a class-level weakness, and none of its children carries one either.

References