CVE-2023-27997

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-06-13), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 3 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
  • Linked to ransomware campaigns
CISA-KEV: ExploitedEPSS PROB: 86%CVSS: 9.8Exploit: Public PoCExposed services: 3

Please upgrade to FortiOS-6K7K version 7.0.12 or above (from the CVE record's solution, Fortinet, Inc.) — apply it.

A heap-based buffer overflow vulnerability [CWE-122] in FortiOS version 7.2.4 and below, version 7.0.11 and below, version 6.4.12 and below, version 6.0.16 and below and FortiProxy version 7.2.3 and below, version 7.0.9 and below, version 2.0.12 and below, version 1.2 all versions, version 1.1 all versions SSL-VPN may allow a remote attacker to execute arbitrary code or commands via specifically crafted requests.

Internet exposure · derived from Shodan data

3 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2023-27997, in our KEV-Exposure radar’s Shodan-derived sample.

across 3 countries (Canada, Thailand, United States)top: fortios🔒 ransomware-linked
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Please upgrade to FortiOS-6K7K version 7.0.12 or above (from the CVE record's solution, Fortinet, Inc.). Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
86%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
86% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

Please upgrade to FortiOS-6K7K version 7.0.12 or above (from the CVE record's solution, Fortinet, Inc.). Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://www.fortiguard.com/psirt/FG-IR-23-097 · https://nvd.nist.gov/vuln/detail/CVE-2023-27997

Published

June 13, 2023

Last Modified

July 31, 2026

Advisory Details (2)

Auto-updated Oct 23, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Fix named in the CVE record's solution (Fortinet, Inc.). Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-27997
Web page

PSIRT | FortiGuard Labs

https://fortiguard.com/psirt/FG-IR-23-097

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 150× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 932 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 832 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 86% · 99th percentile
  2. 2026-10-23 05:53 UTCEG score recompute
  3. 2026-10-23 05:53 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-22 08:01 UTCEG score recompute
  5. 2026-10-22 08:01 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-21 16:29 UTCEPSS rescoreEPSS 86% · 99th percentile
  7. 2026-10-21 10:08 UTCEG score recompute
  8. 2026-10-21 10:08 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-20 12:13 UTCEG score recompute
  10. 2026-10-20 12:13 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-19 16:29 UTCEPSS rescoreEPSS 86% · 99th percentile
  12. 2026-10-19 14:20 UTCEG score recompute
  13. 2026-10-19 14:20 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-18 16:26 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-18 08:07 UTCEG score recompute
  16. 2026-10-17 20:15 UTCEG score recompute
  17. 2026-10-17 20:15 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-16 22:21 UTCEG score recompute
  19. 2026-10-16 22:21 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-16 16:35 UTCEPSS rescoreEPSS 86% · 99th percentile
  21. 2026-10-16 00:28 UTCEG score recompute
  22. 2026-10-16 00:28 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-15 02:36 UTCEG score recompute
  24. 2026-10-15 02:35 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-14 16:29 UTCEPSS rescoreEPSS 86% · 99th percentile
Show 75 more
  1. 2026-10-14 04:43 UTCEG score recompute
  2. 2026-10-14 04:43 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 06:51 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-12 18:30 UTCEG score recompute
  5. 2026-10-12 09:00 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 04:36 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-12 00:12 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-11 19:48 UTCEG score recompute
  9. 2026-10-11 19:48 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-11 15:25 UTCEG score recompute
  11. 2026-10-11 15:25 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-11 11:01 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 06:37 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-11 02:14 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 21:49 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 17:25 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-10 13:02 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-10 08:39 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-10 04:15 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-09 23:51 UTCEG score recompute
  21. 2026-10-09 23:51 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-09 20:05 UTCEPSS rescoreEPSS 86% · 99th percentile
  23. 2026-10-09 19:27 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-09 15:04 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-09 10:41 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-09 06:16 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-09 01:53 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-08 21:30 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-08 17:06 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-08 12:42 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-08 08:18 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-08 03:55 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-07 23:32 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-07 19:08 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-07 14:44 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-07 10:21 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-07 05:58 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-07 01:34 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-06 21:11 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-06 16:48 UTCEG score recompute
  41. 2026-10-06 16:48 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-06 15:15 UTCEPSS rescoreEPSS 86% · 99th percentile
  43. 2026-10-06 12:25 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-06 08:01 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-06 03:39 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-05 23:15 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-05 18:52 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-05 14:29 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-05 10:06 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-05 05:44 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-05 01:21 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-04 20:58 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-04 16:33 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-04 12:09 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-04 07:46 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-04 03:23 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-03 23:00 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-03 18:37 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-03 14:13 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-03 09:49 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-03 05:25 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-03 01:02 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-02 20:39 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-02 16:14 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-02 16:14 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-02 11:49 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-02 07:25 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-02 03:01 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-01 22:36 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-01 18:11 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-01 13:47 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-01 09:24 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-01 05:01 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-01 00:38 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-30 20:16 UTCGHSA enrichmentGHSA-2hj2-fcr9-9p35 · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (4 GitHub PoCs), as are 2 GitHub checker repositories. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub checkerVampsecure-Labs/vamp-forticheck
    Published Jul 31, 2026

    VampSecure Labs: FortiOS CVE scanner (CVE-2018-13379, CVE-2022-40684, CVE-2023-27997, CVE-2024-21762)

    Open source ↗
  • GitHub PoCdelsploit/CVE-2023-27997
    Published Oct 12, 2023
    Open source ↗
  • GitHub PoClexfo/xortigate-cve-2023-27997
    Published Oct 12, 2023

    xortigate-cve-2023-27997

    Open source ↗
  • GitHub PoCTechinsightsPro/ShodanFortiOS
    Published Jul 11, 2023

    Search vulnerable FortiOS devices via Shodan (CVE-2023-27997)

    Open source ↗
  • GitHub checkerBishopFox/CVE-2023-27997-check
    Published Jun 16, 2023

    Safely detect whether a FortiGate SSL VPN instance is vulnerable to CVE-2023-27997 based on response timing

    Open source ↗
  • GitHub PoCrio128128/CVE-2023-27997-POC
    Published Jun 16, 2023

    POC FortiOS SSL-VPN buffer overflow vulnerability

    Open source ↗

Frequently asked(6)

What is CVE-2023-27997?
CVE-2023-27997 is a critical-severity vulnerability; its CVE record was published on June 13, 2023. A heap-based buffer overflow vulnerability [CWE-122] in FortiOS version 7.2.4 and below, version 7.0.11 and below, version 6.4.12 and below, version 6.0.16 and below and FortiProxy version 7.2.3 and below, version 7.0.9 and below, version 2.0.12 and below, version 1.2 all versions, version 1.1 all…
When was the CVE record for CVE-2023-27997 published?
The CVE record for CVE-2023-27997 was published on June 13, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 31, 2026; the record at its source may have been updated since.
Is CVE-2023-27997 actively exploited?
Yes. CISA added CVE-2023-27997 to the Known Exploited Vulnerabilities catalog on June 13, 2023, affecting Fortinet FortiOS and FortiProxy SSL-VPN. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. Please upgrade to FortiOS-6K7K version 7.0.12 or above (from the CVE record's solution, Fortinet, Inc.). Apply it.
What is the CVSS score of CVE-2023-27997?
CVE-2023-27997 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2023-27997?
CVE-2023-27997 affects Fortinet FortiOS and FortiProxy SSL-VPN.
How do I remediate CVE-2023-27997?
The CVE record's solution for CVE-2023-27997, written by its CNA Fortinet, Inc., names the fix: "Please upgrade to FortiOS-6K7K version 7.0.12 or above".

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-27997

Explore →

Is Your Infrastructure Affected by CVE-2023-27997?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.