Back to Labs
Security Advisory

CVE-2022-22963

About

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.

Weakness (CWE):CWE-94CWE-917

Rainforest analyst review

Spring Cloud Function lets clients pick which function handles a request through routing, and the routing target is read from a header expressed in Spring Expression Language. That expression is evaluated without sandboxing, so an attacker who sets a crafted spring.cloud.function.routing-expression header can make the server run arbitrary SpEL, which reaches Java runtime calls and therefore executes operating-system commands and reads local resources. No authentication or user interaction is involved; a single HTTP request carrying the malicious header is enough.

Spring Cloud Function underpins serverless and event-driven Java services, frequently deployed behind API gateways and message brokers where the routing header is exactly the kind of input an attacker can control. It surfaced alongside the Spring4Shell period, drew immediate mass scanning, and sits on CISA's KEV list. Upgrade past 3.1.6 and 3.2.2 to a fixed release. Because the exploit is a simple header on an ordinary request, patching is the real fix; interim header filtering at a proxy is brittle and easy to bypass, so treat it only as a stopgap while you roll out the update.

References

Related CVEs

Frequently asked questions

What is CVE-2022-22963?

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.

How severe is CVE-2022-22963?

CVE-2022-22963 carries a CVSS 3.1 base score of 9.8, rated critical. On the Rainforest Risk Index — which weighs the severity alongside how easy the flaw is to reach and how broad its impact is — it scores 99 out of 100, in the critical band.

How is CVE-2022-22963 exploited?

According to the CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H): attack vector Network, attack complexity Low, privileges required None, user interaction None. Impact on confidentiality High, integrity High and availability High.

Which products are affected by CVE-2022-22963?

Public advisories list the following as affected: banking branch, banking cash management, banking corporate lending process management, banking credit facilities process management, banking electronic data exchange for corporates, banking liquidity management, +22. Check the references on this page for the exact versions each vendor confirms.

How do I fix CVE-2022-22963?

Apply the fix the vendor published — the references on this page link to the primary advisories and patches. When patching can't happen right away, reduce the exposure of the affected component and watch it for exploitation attempts. Rainforest customers see this vulnerability correlated to their own assets and prioritized by real exposure, not by score alone.

Empower Your Security Strategy with Rainforest

Discover vulnerabilities early, prioritize critical threats, and protect what truly matters. Rainforest streamlines your security operations, saving you time and reducing costs, so you can focus on what drives your business forward.

Share this:LinkedInX Email