CVE Tools

CVE-2022-42475

Exploited in the wild. In CISA KEV since 2022‑12‑13. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU, CSAF

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check what Fortinet product you run (FortiOS / FortiProxy) and its exact version, then plan an immediate upgrade to a fixed release.
  2. If you can’t upgrade right away, restrict access to SSL-VPN/FortiProxy (for example, allow only known IP addresses or limit exposure to the internet) with help from your IT provider.
  3. Ask your IT/security person to confirm whether any systems are reachable from the internet and to monitor for signs of unusual activity on the SSL-VPN/FortiProxy services.

What it is

From the CVE record

A heap-based buffer overflow vulnerability [CWE-122] in FortiOS SSL-VPN 7.2.0 through 7.2.2, 7.0.0 through 7.0.8, 6.4.0 through 6.4.10, 6.2.0 through 6.2.11, 6.0.15 and earlier and FortiProxy SSL-VPN 7.2.0 through 7.2.1, 7.0.7 and earlier may allow a remote unauthenticated attacker to execute arbitrary code or commands via specifically crafted requests.

In plain language

Written by AI from the record

CVE-2022-42475 is a critical security flaw in Fortinet FortiOS and FortiProxy SSL-VPN that can let an attacker, without logging in, run code; if you use Fortinet SSL-VPN/ FortiProxy, you should act immediately.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2022-12-13.

US federal agencies must remediate by 2023-01-03.

Known use in ransomware campaigns.

Apply updates per vendor instructions.
Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

99% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 133 days before any public exploit.

  1. OpenVAS check added
  2. Public exploit / PoCsource: othernuclei check added
  3. Patch availableworkaround available, record updated
  4. Publishedweakness classified, att&ck mapped
  5. Added to CISA KEVransomware campaign

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for FortiProxy, not every advisory. This one: actively exploited.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store