dbcve.org
Spring Cloud GatewayFramework / library · VMware

CVE-2021-22051

MEDIUM · 6.5 CVSS v3.1 Published 2021-11-08
Fix available
A fix is available. Upgrade to 2.2.10 / 3.0.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Applications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream services. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.5+, 2.2.x users should upgrade to 2.2.10.RELEASE or newer.

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 confidence

This is an HTTP request smuggling vulnerability in Spring Cloud Gateway. Specifically crafted requests can cause the gateway to make an extra request to downstream services, potentially allowing attackers to smuggle requests through the gateway to access internal services or bypass security controls.

MitigationUpgrade Spring Cloud Gateway to version 3.0.5+ (for 3.0.x users) or 2.2.10.RELEASE+ (for 2.2.x users) to resolve the vulnerability.

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 GatewayFramework / library
Affected:< 2.2.10>= 3.0.0, < 3.0.5

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Spring Cloud Gateway is deployed
    Locate the Spring Cloud Gateway application JAR file or container image. Check project dependencies (Maven pom.xml, Gradle build.gradle) for spring-cloud-gateway dependency.
    Affected if Spring Cloud Gateway is not present in the environment, the CVE does not apply.
  2. Identify the installed version
    For JAR deployments, run: java -jar <gateway-jar-file>.jar --version or inspect the JAR manifest (META-INF/MANIFEST.MF). For Maven/Gradle projects, check the effective POM or lock file for spring-cloud-gateway version.
    Affected if Unable to determine the version - manual inspection required.
  3. Compare version against affected ranges
    Match the identified version to these vulnerable ranges: 3.0.0 through 3.0.4 (inclusive), or any version below 2.2.10 in the 2.2.x line.
    Affected if Version falls within < 2.2.10 OR (>= 3.0.0 AND < 3.0.5). Versions 3.0.5+ and 2.2.10+ are NOT affected.
  4. Verify HTTP gateway exposure
    Inspect the gateway configuration (application.yml or application.properties) for server.port bindings and any proxy/route definitions that accept external HTTP requests.
    Affected if The gateway listens on a port exposed to untrusted network traffic (including load balancers, proxies, or direct internet exposure).

Environment is affected if Spring Cloud Gateway is deployed with a version below 2.2.10 or between 3.0.0 and 3.0.4 inclusive, and the gateway accepts HTTP requests from external or untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.10 / 3.0.5 or later
Fixed in 2.2.103.0.5
Interim mitigation

Upgrade Spring Cloud Gateway to version 3.0.5+ (for 3.0.x users) or 2.2.10.RELEASE+ (for 2.2.x users) to resolve the vulnerability.

Recommended fix High confidence

2.2.10.RELEASE for 2.2.x line; 3.0.5 for 3.0.x line

  1. Identify the current Spring Cloud Gateway version in your project's dependency management (e.g., pom.xml, build.gradle)
  2. If using 2.2.x line (version < 2.2.10): Update the Spring Cloud Gateway dependency to version 2.2.10.RELEASE or newer
  3. If using 3.0.x line (version >= 3.0.0 and < 3.0.5): Update the Spring Cloud Gateway dependency to version 3.0.5 or newer
  4. Update parent POM or dependency management section with the corresponding Spring Cloud version that includes the fixed gateway version
  5. Run dependency resolution to confirm the correct version is resolved
  6. Rebuild and redeploy the application
  7. Verify the application functions normally after the upgrade
Caveat Minor release upgrades within same major version typically have low risk, but review Spring Cloud release notes for any behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Cloud Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22051 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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