How severe is CVE-2020-5412?

CVE-2020-5412 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-5412?

CVE-2020-5412 affects the following packages: org.springframework.cloud:spring-cloud-netflix (Maven), org.springframework.cloud:spring-cloud-netflix (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-5412?

Update org.springframework.cloud:spring-cloud-netflix to 2.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-5412 is resolved across your whole dependency graph.

How do I detect CVE-2020-5412 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-netflix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-5412 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2020-5412 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-5412 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-5412?

CVE-2020-5412 has an EPSS (Exploit Prediction Scoring System) score of 10.2%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2020-5412?

CVE-2020-5412 is classified as CWE-441 (CWE-441), CWE-610 (CWE-610). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2020-5412?

A Nuclei detection template exists for CVE-2020-5412, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-5412 published, and has it been updated?

CVE-2020-5412 was published on August 7, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-5412 — spring-cloud-netflix

MEDIUM

CVE-2020-5412 is a medium-severity (CVSS 6.5) CWE-441 vulnerability in org.springframework.cloud:spring-cloud-netflix. EPSS puts its 30-day exploitation probability at 10.2% (96th percentile). A fix is available for org.springframework.cloud:spring-cloud-netflix — see the affected versions and patch details below.

Externally Controlled Reference to a Resource in Another Sphere and Confused Deputy in Spring Cloud Netflix

Also known asGHSA-qgcg-p3v2-9h4p

Published

Aug 7, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

10.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-5412 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.springframework.cloud:spring-cloud-netflix☕org.springframework.cloud:spring-cloud-netflix

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Spring Cloud Netflix, versions 2.2.x prior to 2.2.4, versions 2.1.x prior to 2.1.6, and older unsupported versions allow applications to use the Hystrix Dashboard proxy.stream endpoint to make requests to any server reachable by the server hosting the dashboard. A malicious user, or attacker, can send a request to other servers that should not be exposed publicly.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.cloud:spring-cloud-netflix`	≥ 2.2.0&&< 2.2.4	2.2.4`org.springframework.cloud:spring-cloud-netflix:2.2.4`
☕Maven	`org.springframework.cloud:spring-cloud-netflix`	≥ 2.1.0&&< 2.1.6	2.1.6`org.springframework.cloud:spring-cloud-netflix:2.1.6`

Affected Products

1 product · 2 configurations

Application

spring cloud netflixvmware

≥ 2.2.0 && < 2.2.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-netflix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.cloud:spring-cloud-netflix to 2.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-5412 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2020-5412

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2020-5412 -u https://target

Template: Spring Cloud Netflix - Server-Side Request Forgery
Severity: medium
Impact: The vulnerability can result in unauthorized access to sensitive data or systems, leading to potential data breaches or further exploitation.
Remediation: Apply the latest security patches or updates provided by Spring Cloud Netflix to mitigate the vulnerability.

Template by ProjectDiscovery nuclei-templates (dwisiswant0), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-5412 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-441CWE-441 CWE-610CWE-610

Weaponization

Timeline

Disclosed

Aug 7, 2020

Last updated

Jul 8, 2026

Identifiers

CVE-2020-5412

GHSA-qgcg-p3v2-9h4p

References

Advisorytanzu.vmware.com Advisorynvd.nist.gov

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-441 are rated as high or higher (top: high).

CVE-2026-86003CVE-2026-61793CVE-2026-78682CVE-2026-63643CVE-2026-54663CVE-2026-43910CVE-2026-73424CVE-2026-54628Browse all CWE-441

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2020-5412 — spring-cloud-netflix

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2020-5412

Frequently Asked Questions

Is CVE-2020-5412 in your dependencies?