Spring Cloud FunctionFramework / library · VMware

CVE-2022-22963

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-01

Fix available

A fix is available. Upgrade to after 3.2.2 or later.

See remediation →

100/100

Remediation priority · Urgent

In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

In Spring Cloud Function versions 3.1.6, 3.2.2 and older unsupported versions, when using routing functionality it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to local resources.

Technical summary

dbcve analysis · high confidence

Spring Cloud Function versions 3.1.6, 3.2.2 and older contain a SpEL injection vulnerability in the routing functionality. Attackers can supply specially crafted Spring Expression Language (SpEL) in the routing-expression parameter to achieve remote code execution and access local file system resources.

MitigationUpgrade Spring Cloud Function to version 3.1.7, 3.2.3, or later which contain the security patch. If upgrading is not immediately possible, disable the routing functionality and/or implement web application firewall rules to block requests with malicious SpEL expressions in routing headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Spring Cloud FunctionFramework / library

Affected:<= 3.1.6>= 3.2.0, <= 3.2.2

Banking BranchApplication

Affected:= 14.5

Banking Cash ManagementApplication

Affected:= 14.5

Banking Corporate Lending Process ManagementApplication

Affected:= 14.5

Banking Credit Facilities Process ManagementApplication

Affected:= 14.5

Banking Electronic Data Exchange For CorporatesApplication

Affected:= 14.5

Banking Liquidity ManagementApplication

Affected:= 14.2= 14.5

Banking OriginationApplication

Affected:= 14.5

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Identify Spring Cloud Function installation

Search for spring-cloud-function-core JAR in the classpath, check pom.xml or build.gradle dependencies for 'spring-cloud-function', or look for Spring Cloud Function banner in application startup logs

Affected if Spring Cloud Function is present in the application
Determine installed version

Inspect the version of spring-cloud-function-core JAR, Maven dependency tree, or the spring-cloud-function JAR manifest. Compare against affected versions: <= 3.1.6 or >= 3.2.0 through <= 3.2.2

Affected if Version is 3.1.6 or lower, OR between 3.2.0 and 3.2.2 inclusive
Check if routing functionality is enabled

Inspect application.properties or application.yml for 'spring.cloud.function.routing.enabled=true' or look for 'functionRouter' bean definition. Also check if spring.cloud.function.definition or spring.cloud.function.routing-expression configuration is present

Affected if Routing is enabled (either explicitly via configuration or via functionRouter bean definition)
Verify routing-expression parameter processing

Monitor HTTP requests for 'routing-expression' header or parameter being processed by the application. Check access logs or enable debug logging for org.springframework.cloud.function.web.mvc

Affected if The application processes the routing-expression parameter from incoming requests

The environment is affected if Spring Cloud Function version is 3.1.6 or lower, or between 3.2.0 and 3.2.2, AND the routing functionality is enabled allowing the routing-expression parameter to be processed.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 3.2.2

Vendor patch www.oracle.com →

Interim mitigation

Upgrade Spring Cloud Function to version 3.1.7, 3.2.3, or later which contain the security patch. If upgrading is not immediately possible, disable the routing functionality and/or implement web application firewall rules to block requests with malicious SpEL expressions in routing headers.

Recommended fix High confidence

Spring Cloud Function 3.1.7 or 3.2.3 (or later)

1. Identify all applications using Spring Cloud Function versions 3.1.6 or earlier, or 3.2.0-3.2.2
2. For Spring Cloud Function: Upgrade to version 3.1.7 or 3.2.3 (or later) which contain the fix for CVE-2022-22963
3. For Oracle Banking products: Apply the corresponding Oracle Critical Patch Update for the specific affected module (Banking Branch 14.5, Banking Liquidity Management 14.2/14.5, etc.)
4. After upgrading, verify that routing functionality still works correctly with legitimate routing expressions
5. Ensure that user-supplied input is not directly used in SpEL expressions without proper sanitization
6. Monitor for any indicators of compromise and review application logs for suspicious SpEL-related requests

Caveat Upgrading Spring Cloud Function may introduce breaking changes; review the release notes for the target version for any backward-incompatible changes in your specific function implementations

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

Fix this in Spring Cloud Function Exploited in the wild — priority engagement

Consultation2.0 h
Implementation4.0 h
Testing6.0 h
Review / QA2.0 h

14.0 hours of engineering $2,380

Get it fixed fast

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comPatch / commit
packetstormsecurity.comProof of Concept
tanzu.vmware.comVendor Advisory
www.oracle.comPatchThird Party Advisory
www.oracle.comPatchThird Party Advisory
packetstormsecurity.comExploitThird Party AdvisoryVDB Entry
psirt.global.sonicwall.comThird Party Advisory
tools.cisco.comThird Party Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-22963?

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.

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

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2022-09-15

A fix existsUpgrade to after 3.2.2 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 99.9%

Affects: Spring Cloud Function

Remediation

Being exploited — close it fast

Fix this in Spring Cloud Function 14 hrs · Moderate

Typical engagement from $2,380

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References