Security readout for executives and security teams
Plain-English summary
This flaw can let an unauthenticated remote user bypass Fortinet DNS filtering when traffic comes from Apple devices. It is not a device takeover issue, but it can undermine web and DNS policy enforcement where FortiOS or FortiProxy is used to block risky destinations.
Executive priority
Treat this as a moderate policy-control failure. It should be scheduled promptly where DNS filtering is a required security control, compliance control, or child-safety/business-use control, but it does not carry the urgency of Fortinet remote code execution vulnerabilities.
Technical view
CVE-2024-55599 is a CWE-358 improper security check issue in FortiOS and FortiProxy. The published CVSS 3.1 score is 4.9, with network attack vector, low complexity, no privileges, no user interaction, and low integrity impact only.
Likely exposure
Exposure is most relevant for organizations using FortiOS or FortiProxy DNS filtering with Apple devices. The bundle lists FortiOS 7.6.0, 7.4.7 and below, 7.2.x CPEs, all 7.0 and 6.4 versions, and FortiProxy 7.6.1 and below, 7.4.8 and below, and all 7.2 and 7.0 versions.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The issue is remotely reachable and unauthenticated, but the documented impact is bypassing DNS filtering, not code execution, authentication bypass to management, or data disclosure.
Researcher notes
Evidence is limited to the CVE bundle and cited advisories. The bundle does not provide technical root-cause details, proof-of-concept status, fixed release numbers, or vendor workarounds. Avoid assuming broader Fortinet exposure beyond FortiOS and FortiProxy DNS filtering behavior.
Mitigation direction
- Review Fortinet PSIRT FG-IR-24-053 for fixed versions and vendor-supported workarounds.
- Upgrade affected FortiOS and FortiProxy systems according to Fortinet guidance.
- Check Siemens SSA-864900 if Fortinet components are embedded in managed or industrial environments.
- Document any temporary exceptions where Apple device DNS filtering cannot be immediately remediated.
Validation and detection
- Inventory FortiOS and FortiProxy versions against the affected ranges in the CVE bundle.
- Confirm whether DNS filtering is enabled and used for Apple device traffic.
- Review Fortinet advisory status for each affected release branch before closing the finding.
- Monitor policy logs for unexpected DNS filter bypasses involving Apple clients.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-358: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-55599 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:X/RC:X
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:X/RC:X3.91.4fortinetVulnerability scoring details
Base CVSS 3.1 score
4.9MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:X/RC:X
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://fortiguard.fortinet.com/psirt/FG-IR-24-053CVE reference, fortinet
- https://cert-portal.siemens.com/productcert/html/ssa-864900.htmlCVE reference, siemens-SADP
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improperly Implemented Security Check for Standard
Improperly Implemented Security Check for Standard represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.