Spring Cloud NetflixFramework / library · VMware
CVE-2020-5412
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Hystrix Dashboard proxy.stream endpoint in Spring Cloud Netflix versions prior to 2.2.4 and 2.1.6 lacks proper validation, allowing remote attackers to abuse the dashboard server as a proxy to make arbitrary HTTP requests to internal services reachable by the host (Server-Side Request Forgery). This exposes infrastructure that should remain internal.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring Cloud NetflixFramework / library
< 2.1.6>= 2.2.0, < 2.2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Cloud Netflix usageSearch your project dependencies (Maven pom.xml, Gradle build.gradle, or application classpath) for the spring-cloud-starter-netflix-hystrix-dashboard or netflix-hystrix dependency.Affected if The dependency is present in your project.
-
Determine the installed Spring Cloud Netflix versionLocate the netflix-hystrix or spring-cloud-netflix version in your dependency management (pom.xml, build.gradle, or a BOM file) and note the exact version number.Affected if The version is less than 2.1.6, or greater than or equal to 2.2.0 but less than 2.2.4.
-
Verify Hystrix Dashboard is enabledCheck if @EnableHystrixDashboard annotation is present in your configuration or if the Hystrix Dashboard endpoint (/hystrix or /proxy.stream) is registered and accessible in your application.Affected if The Hystrix Dashboard is enabled and the endpoint is accessible.
-
Confirm network exposure of the dashboardReview your web server or firewall configuration to determine whether the Hystrix Dashboard endpoint is reachable from network sources other than localhost/trusted internal clients.Affected if The /hystrix or /proxy.stream endpoint is exposed to untrusted network traffic.
Your environment is affected if it uses Spring Cloud Netflix with a version in the vulnerable range AND has the Hystrix Dashboard enabled and accessible to untrusted network sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.1.62.2.4
Upgrade Spring Cloud Netflix to version 2.2.4 or 2.1.6 or later; alternatively, if the Hystrix Dashboard cannot be upgraded, restrict network access to the dashboard to trusted clients only or disable it entirely.
Fix this in Spring Cloud Netflix
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5412 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5412 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data