Is CVE-2022-22963 exploited in the wild?

Yes. CVE-2022-22963 is known to be exploited in the wild, first recorded on 25 August 2022. Treat it as urgent.

How severe is CVE-2022-22963?

Critical severity, with a CVSS score of 3.1, published 3 April 2022.

Which products and versions are affected?

org.springframework.cloud:spring-cloud-function-context (Maven) ECOSYSTEM:introduced=3.2.0,fixed=3.2.3.

Is there a fix for CVE-2022-22963?

Yes. org.springframework.cloud:spring-cloud-function-context (Maven): upgrade to 3.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2022-22963 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2022-22963?

Check whether you run org.springframework.cloud:spring-cloud-function-context (Maven) or VMware Tanzu Spring Cloud at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2022-22963: Spring Cloud Function Code Injection with a specially crafted SpEL as a routing expression

CVE-2022-22963 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2022-04-03

VMware Tanzu Spring Cloud Function contains a remote code execution vulnerability in its routing functionality. An attacker can provide a specially crafted SpEL (Spring Expression Language) as a routing-expression to execute arbitrary code and access local resources.

Technologies: org.springframework.cloud:spring-cloud-function-context (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-22963 exploited in the wild?: Yes. CVE-2022-22963 is known to be exploited in the wild, first recorded on 25 August 2022. Treat it as urgent.
How severe is CVE-2022-22963?: Critical severity, with a CVSS score of 3.1, published 3 April 2022.
Which products and versions are affected?: org.springframework.cloud:spring-cloud-function-context (Maven) ECOSYSTEM:introduced=3.2.0,fixed=3.2.3.
Is there a fix for CVE-2022-22963?: Yes. org.springframework.cloud:spring-cloud-function-context (Maven): upgrade to 3.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2022-22963 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2022-22963?: Check whether you run org.springframework.cloud:spring-cloud-function-context (Maven) or VMware Tanzu Spring Cloud at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.cloud:spring-cloud-function-context (Maven): upgrade to 3.2.3 or later

# set org.springframework.cloud:spring-cloud-function-context to 3.2.3 in your pom.xml or build.gradle

Affected products

VMware Spring Cloud Function 3.1.6, 3.2.2 and older unsupported versions

Identifiers

CVE-2022-22963
GHSA-6v73-fgf6-w5j7

Timeline

2022-08-25: disclosed
2022-08-25: advisory
2022-08-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.