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
Affects Spring Cloud Function before 3.1.7 and 3.2.0 through 3.2.2 when routing functionality is used. The fix is in 3.1.7 and 3.2.3. No vendor severity rating is given.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 3.2.3, 3.1.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Spring Cloud Function, a Java framework for building serverless-style functions, is affected when its routing feature is used. An attacker who can supply a specially crafted routing expression could execute arbitrary code on the server and access local resources.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- n/a Spring Cloud Function
Spring Cloud Function versions 3.1.6, 3.2.2 and all old and unsupported versions
- org.springframework.cloud:spring-cloud-function-contextMaven
From 3.2.0 · fixed in 3.2.3
- org.springframework.cloud:spring-cloud-function-contextMaven
fixed in 3.1.7
References 6
tanzu.vmware.com
psirt.global.sonicwall.com
packetstormsecurity.com
Questions about CVE-2022-22963
What does this mean?
The advisory says that a user can, through the routing functionality of Spring Cloud Function, cause a result that may lead to remote code execution and access to local resources.Source: spring.io
Am I affected, and how do I check?
Versions 3.1.6 and older unsupported versions, and 3.2.0 through 3.2.2, are in the affected ranges, but only where routing functionality is used. To check, look at the spring-cloud-function-context version in your build file or dependency tree, and check whether your code uses routing functions.Source: spring.io
What should I do about it?
Upgrade spring-cloud-function-context to 3.1.7 if you are on the 3.1 line, or to 3.2.3 if you are on the 3.2 line.Source: spring.io
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-08-25, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data