Spring Cloud GatewayFramework / library · VMware
CVE-2022-22947
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 · uneditedIn spring cloud gateway versions prior to 3.1.1+ and 3.0.7+ , applications are vulnerable to a code injection attack when the Gateway Actuator endpoint is enabled, exposed and unsecured. A remote attacker could make a maliciously crafted request that could allow arbitrary remote execution on the remote host.
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 confidenceSpring Cloud Gateway contains a code injection vulnerability that allows remote attackers to execute arbitrary code by sending malicious requests to the Gateway Actuator endpoint when it is exposed and unsecured. This affects versions prior to 3.1.1+ and 3.0.7+.
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
< 3.0.7= 3.1.0= 11.3.2= 1.11.0= 22.1.3= 22.2.0= 22.1.0= 1.10.0= 1.15.0= 1.15.1= 22.1.2= 22.2.0= 1.8.0= 22.1.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 if Spring Cloud Gateway is deployedLook for Spring Cloud Gateway processes or applications in your environment. Check for JAR files with 'spring-cloud-gateway' in the name, or containers running Spring Cloud Gateway images.Affected if Spring Cloud Gateway is present in the environment
-
Check the installed Spring Cloud Gateway versionReview your build artifacts, dependency management files (pom.xml, build.gradle), or examine the JAR manifest. Compare the version against the affected ranges: versions < 3.0.7 or version 3.1.0.Affected if The version is less than 3.0.7 or equals 3.1.0
-
Verify if the Gateway Actuator endpoint is enabledExamine your application configuration files (application.properties or application.yml) for the presence of 'management.endpoint.gateway.enabled=true' or any gateway actuator configuration.Affected if The gateway actuator endpoint is explicitly enabled in the configuration
-
Confirm if actuator endpoints are exposed without authenticationReview your management configuration for 'management.endpoints.web.exposure.include' and verify whether 'gateway' or '*' is included. Check that Spring Security is properly configured to require authentication for these endpoints, or that network access controls prevent unauthorized access.Affected if The gateway actuator is exposed (included in web exposure) and either has no authentication configured or is accessible from untrusted networks
You are affected if you run a vulnerable Spring Cloud Gateway version (less than 3.0.7 or exactly 3.1.0) AND the gateway actuator endpoint is enabled and accessible without authentication.
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.
dbcve · scoped3.0.7
Secure or disable the Gateway Actuator endpoint (e.g., via Spring Security filters or network segmentation), or upgrade Spring Cloud Gateway to version 3.1.1+ or 3.0.7+ which contains the patch.
Spring Cloud Gateway 3.0.7+ or 3.1.1+ (Oracle products: apply Oracle CPU patches for listed versions)
- 1. Identify all Spring Cloud Gateway deployments in your environment and verify the current version by checking the Spring Cloud Gateway JAR or pom.xml
- 2. Determine if the Gateway Actuator endpoint is enabled by checking application.properties or application.yml for 'management.endpoint.gateway.enabled=true' (or defaults to true)
- 3. If actuator endpoints are exposed externally (e.g., not restricted by network or authentication), this is critical exposure - restrict access immediately or disable if not needed
- 4. Upgrade Spring Cloud Gateway to version 3.0.7 or higher (3.0.x users) OR version 3.1.1 or higher (3.1.x users)
- 5. After upgrade, verify the fix by reviewing release notes and testing that actuator endpoints are properly secured with authentication and network restrictions
- 6. For Oracle Communications products listed, apply the corresponding Oracle Critical Patch Update that addresses this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Cloud Gateway
Exploited in the wild — priority engagement
- 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-2022-22947 — 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-2022-22947 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