dbcve.org
Spring Cloud OpenfeignFramework / library · VMware

CVE-2021-22044

HIGH · 7.5 CVSS v3.1 Published 2021-10-28
Fix available
A fix is available. Upgrade to after 3.0.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
In Spring Cloud OpenFeign 3.0.0 to 3.0.4, 2.2.0.RELEASE to 2.2.9.RELEASE, and older unsupported versions, applications using type-level `@RequestMapping`annotations over Feign client interfaces, can be involuntarily exposing endpoints corresponding to `@RequestMapping`-annotated interface methods.

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

Applications using type-level @RequestMapping annotations on Spring Cloud OpenFeign client interfaces inadvertently expose those interface methods as accessible HTTP endpoints. This allows unintended internal API methods to be callable over the network, potentially exposing sensitive functionality.

MitigationUpgrade to Spring Cloud OpenFeign 3.0.5+, 2.2.10+, or later patched versions. Alternatively, review and remove type-level @RequestMapping annotations from Feign client interfaces if upgrading is not immediately feasible.

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 OpenfeignFramework / library
Affected:>= 2.2.0, <= 2.2.9>= 3.0.0, <= 3.0.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify Spring Cloud OpenFeign version in use
    Inspect your Maven pom.xml, Gradle build.gradle, or application dependencies for the spring-cloud-openfeign-core library version number. Search for entries like 'org.springframework.cloud:spring-cloud-openfeign-core' and note the declared version.
    Affected if The detected version falls within 2.2.0 through 2.2.9, or 3.0.0 through 3.0.4.
  2. Locate Feign client interface definitions
    Search your codebase for Java interfaces annotated with @FeignClient. Search patterns include '@FeignClient' and '@Client' annotations from Spring Cloud OpenFeign packages.
    Affected if At least one Feign client interface exists in your project.
  3. Inspect Feign interfaces for type-level @RequestMapping
    For each @FeignClient interface found, examine whether the interface itself (not just its methods) has a @RequestMapping annotation. Look for '@RequestMapping' appearing directly above 'interface YourClientName'. Also check for @GetMapping, @PostMapping, @PutMapping, @DeleteMapping at type level.
    Affected if Any @FeignClient interface has @RequestMapping, @GetMapping, @PostMapping, @PutMapping, or @DeleteMapping applied at the type (class/interface) level.
  4. Verify exposed endpoints are network-accessible
    If type-level mapping exists, confirm whether your Spring application exposes HTTP endpoints externally (check server.address, server.port settings, and any API gateway or load balancer configuration). Try accessing the constructed URL path (from the type-level mapping) to confirm it responds.
    Affected if The application runs with accessible network ports AND the type-level mapped path responds to HTTP requests.

You are affected if your Spring Cloud OpenFeign version is 2.2.0-2.2.9 or 3.0.0-3.0.4 AND you have any @FeignClient interface with @RequestMapping or similar mapping annotations at the type level, making those internal methods callable as HTTP endpoints.

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 a release after 3.0.4
Interim mitigation

Upgrade to Spring Cloud OpenFeign 3.0.5+, 2.2.10+, or later patched versions. Alternatively, review and remove type-level @RequestMapping annotations from Feign client interfaces if upgrading is not immediately feasible.

Recommended fix High confidence

Spring Cloud OpenFeign 2.2.10.RELEASE (for 2.2.x users) or 3.0.5 (for 3.0.x users)

  1. 1. Identify the Spring Cloud OpenFeign version currently in use by checking project dependencies (e.g., pom.xml, build.gradle)
  2. 2. Determine which release train line is in use: 2.2.x line or 3.0.x line
  3. 3. For projects using 2.2.x line: upgrade spring-cloud-starter-openfeign dependency to version 2.2.10.RELEASE or later
  4. 4. For projects using 3.0.x line: upgrade spring-cloud-starter-openfeign dependency to version 3.0.5 or later
  5. 5. Rebuild and test the application to verify functionality remains intact
  6. 6. Deploy the updated application
Caveat Patch releases typically contain no breaking changes; however, regression testing is recommended to confirm

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

Fix this in Spring Cloud Openfeign Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22044 — 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-22044 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