CVE Tools

CVE-2020-5397

CSRF Attack via CORS Preflight Requests with Spring MVC or Spring WebFlux

Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.

Check it yourself

Nuclei · 1 templateOpenVAS · 3 checks

e.g. Spring Framework CSRF via CORS Preflight · OID 1.3.6.1.4.1.25623.1.0.104252

Run the check

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

What to do

Find your product and version, then upgrade to the build on the right.

  • Spring FrameworkAffected: ≥ 5.2, < v5.2.3.RELEASEUpgrade to: v5.2.3.RELEASEStated by: CVE record
  • Maven org.springframework:spring-webmvcAffected: ≥ 5.2.0, < 5.2.3Upgrade to: 5.2.3Stated by: GitHub advisory
  • Maven org.springframework:spring-webfluxAffected: ≥ 5.2.0, < 5.2.3Upgrade to: 5.2.3Stated by: GitHub advisory
  • Vmware Spring FrameworkAffected: ≥ 5.2.0, < 5.2.3Upgrade to: 5.2.3Stated by: NVD
  • Oracle Communications Diameter Signaling RouterAffected: ≥ 8.0.0, ≤ 8.2.2Upgrade to: after 8.2.2Stated by: NVD

Versions as the sources state them. 17 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

Spring Framework, versions 5.2.x prior to 5.2.3 are vulnerable to CSRF attacks through CORS preflight requests that target Spring MVC (spring-webmvc module) or Spring WebFlux (spring-webflux module) endpoints. Only non-authenticated endpoints are vulnerable because preflight requests should not include credentials and therefore requests should fail authentication. However a notable exception to this are Chrome based browsers when using client certificates for authentication since Chrome sends TLS client certificates in CORS preflight requests in violation of spec requirements. No HTTP body can be sent or received as a result of this attack.

In plain language

No plain-language summary for this CVE yet.

Exploitation

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

EPSS85th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

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

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

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

Lifecycle

The patch came 471 days before any public exploit.

  1. OpenVAS check added
  2. Public exploit / PoCsource: othernuclei check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 5.3 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 NoneNo confidentiality impact
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

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 serious one reaches you without reading every advisory.

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