Summary
VMware SpringSource Spring Framework before 2.5.6.SEC03, 2.5.7.SR023, and 3.x before 3.0.6, when a container supports Expression Language (EL), evaluates EL expressions in tags twice, which allows remote attackers to obtain sensitive information via a (1) name attribute in a (a) spring:hasBindErrors tag; (2) path attribute in a (b) spring:bind or (c) spring:nestedpath tag; (3) arguments, (4) code, (5) text, (6) var, (7) scope, or (8) message attribute in a (d) spring:message or (e) spring:theme tag; or (9) var, (10) scope, or (11) value attribute in a (f) spring:transform tag, aka "Expression Language Injection."
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
org.springframework:spring-core to 3.0.6 or later; org.springframework:spring-core to 2.5.6.SEC03 or later; org.springframework:spring-core to 2.5.7.SR023 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2011-2730? CVE-2011-2730 is a high-severity security vulnerability in org.springframework:spring-core (maven), affecting versions >= 3.0.0, < 3.0.6. It is fixed in 3.0.6, 2.5.6.SEC03, 2.5.7.SR023.
- Which versions of org.springframework:spring-core are affected by CVE-2011-2730? org.springframework:spring-core (maven) versions >= 3.0.0, < 3.0.6 is affected.
- Is there a fix for CVE-2011-2730? Yes. CVE-2011-2730 is fixed in 3.0.6, 2.5.6.SEC03, 2.5.7.SR023. Upgrade to this version or later.
- Is CVE-2011-2730 exploitable, and should I be worried? Whether CVE-2011-2730 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2011-2730 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2011-2730?
- Upgrade
org.springframework:spring-coreto 3.0.6 or later - Upgrade
org.springframework:spring-coreto 2.5.6.SEC03 or later - Upgrade
org.springframework:spring-coreto 2.5.7.SR023 or later
- Upgrade