Skip to content

GHSA-9ccm-g362-2r35 CVE-2011-2088

XWork in Apache Struts Reveals Sensitive Information

Medium Maven
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
6.14%
Chance of exploitation in the next 30 days. Higher than 93.46% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
2.2.2
Upgrade org.apache.struts.xwork:xwork-core to this version or later

Description

XWork 2.2.1 in Apache Struts 2.2.1, and OpenSymphony XWork in OpenSymphony WebWork, allows remote attackers to obtain potentially sensitive information about internal Java class paths via vectors involving an s:submit element and a nonexistent method, a different vulnerability than CVE-2011-1772.3.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.struts.xwork:xwork-core
< 2.2.2
2.2.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.struts.xwork:xwork-core Maven → 2.2.2

maven
<dependency><groupId>org.apache.struts.xwork</groupId><artifactId>xwork-core</artifactId><version>2.2.2</version></dependency>
gradle
implementation("org.apache.struts.xwork:xwork-core:2.2.2")

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-4wrr-9h5r-m92w
Apache Struts Remote Java Code Execution
Critical Known exploited Also affects org.apache.struts.xwork:xwork-core
GHSA-qcfc-hmrc-59x7
Apache Struts 2 is Missing XML Validation
High Also affects org.apache.struts.xwork:xwork-core
GHSA-wm8w-qp2f-728q
Apache Struts Open Redirect
High Also affects org.apache.struts.xwork:xwork-core
GHSA-hrgc-54mv-58gv
Denial of service in Apache Struts
Medium Also affects org.apache.struts.xwork:xwork-core
GHSA-q2cg-xf9p-h457
Incomplete exclude pattern in Apache Struts
High Also affects org.apache.struts.xwork:xwork-core
GHSA-38qw-j787-v8c2
Apache Struts CSRF Vulnerability
High Also affects org.apache.struts.xwork:xwork-core
GHSA-gqqm-564f-vvxq
Arbitrary code execution in Apache Struts 2
High Also affects org.apache.struts.xwork:xwork-core
GHSA-pw8r-x2qm-3h5m
Arbitrary code execution in Apache Struts 2
High Also affects org.apache.struts.xwork:xwork-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor