Security readout for executives and security teams
Plain-English summary
CVE-2023-42789 is a critical Fortinet vulnerability that can let an unauthenticated network attacker run unauthorized code or commands through crafted HTTP requests. It affects specified FortiOS, FortiProxy, and FortiSASE versions. Because these products often sit at network boundaries, exposed systems should be treated as urgent remediation targets.
Executive priority
Prioritize this as an emergency perimeter-device vulnerability. The impact is full compromise potential, requires no authentication, and affects widely deployed security infrastructure. Absence from KEV lowers confidence of known exploitation, not business impact.
Technical view
The issue is an out-of-bounds write, CWE-787, in affected Fortinet products. CVSS 3.1 is 9.3 with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact. The provided sources identify exploit maturity as proof-of-concept, but do not provide operational exploit details.
Likely exposure
Organizations running affected FortiOS 7.4.0-7.4.1, 7.2.0-7.2.5, 7.0.0-7.0.12, 6.4.0-6.4.14, 6.2.0-6.2.15; affected FortiProxy versions; or FortiSASE 23.2.b may be exposed, especially where HTTP-accessible services are reachable from untrusted networks.
Exploitation context
The source bundle does not show CISA KEV listing and does not cite confirmed active exploitation. It does state remote, unauthenticated exploitation via specially crafted HTTP requests and proof-of-concept exploit maturity in the CVSS vector. Treat internet-facing instances as high-risk until validated and remediated.
Researcher notes
Evidence is strong for affected products, severity, attack vector, and impact. The provided bundle does not include fixed version numbers or detailed workarounds, so remediation should be tied directly to Fortinet FG-IR-23-328. Avoid assuming active exploitation without new cited evidence.
Mitigation direction
- Identify all FortiOS, FortiProxy, and FortiSASE deployments and versions.
- Compare installed versions against the affected ranges in Fortinet FG-IR-23-328.
- Follow Fortinet’s advisory for fixed releases or vendor-approved mitigation.
- Reduce untrusted HTTP exposure to affected management or service interfaces where possible.
- Prioritize internet-facing and security-boundary devices first.
Validation and detection
- Confirm each device product and exact firmware version from trusted inventory or console data.
- Check whether versions fall within the affected ranges listed for this CVE.
- Review Fortinet advisory FG-IR-23-328 for official upgrade targets.
- Search security logs for unusual HTTP requests against Fortinet interfaces.
- Document remediation status for each affected asset.
Public sources used
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-787: 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-2023-42789 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
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
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:H/I:H/A:H/E:P/RL:O/RC:C3.95.9fortinetVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
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.com/psirt/FG-IR-23-328CVE reference, fortinet
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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.