GHSA-wp4h-pvgw-5727 CVE-2019-0230
Improperly Controlled Modification of Dynamically-Determined Object Attributes in Apache Struts
Critical
Maven
- Severity
- 9.8 / 10
- Critical · CVSS 3.1
- Exploit chance (EPSS)
- 96.95%
- Chance of exploitation in the next 30 days. Higher than 99.89% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
- CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
- Fix
2.5.22- Upgrade org.apache.struts:struts2-core to this version or later
Description
Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.struts:struts2-core | >= 2.0.0, < 2.5.22 |
2.5.22 |
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:struts2-core Maven → 2.5.22
- maven
<dependency><groupId>org.apache.struts</groupId><artifactId>struts2-core</artifactId><version>2.5.22</version></dependency>- gradle
implementation("org.apache.struts:struts2-core:2.5.22")
Severity breakdown
CVSS 3.1 9.8
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
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
How to prevent it
- Implementation: By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
- Architecture and Design: By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
- Implementation: When handling untrusted objects, validating using a schema can be used.
- Implementation: By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.
- Implementation: Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.
CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
How to prevent it
- Implementation: If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.
- Architecture and Design, Implementation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- Implementation: For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
- Implementation, Architecture and Design: Refactor the code so that object attributes or fields do not need to be dynamically identified, and only expose getter/setter functionality for the intended attributes.
References
Advisories
Packages
Other links
- cwiki.apache.org/confluence/display/ww/s2-059
- launchpad.support.sap.com
- lists.apache.org/thread.html/r1125f3044a0946d1e7e6f125a6170b58d413ebd4a95157e4608041c…
- lists.apache.org/thread.html/r90890afea72a9571d666820b2fe5942a0a5f86be406fa31da3dd092…
- oracle.com/security-alerts/cpuApr2021.html
- oracle.com/security-alerts/cpujan2021.html
- oracle.com/security-alerts/cpuoct2021.html
- packetstormsecurity.com/files/160108/Apache-Struts-2.5.20-Double-OGNL-Evaluation.html
- packetstormsecurity.com/files/160721/Apache-Struts-2-Forced-Multi-OGNL-Evaluation.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-8c6j-ffmf-q6vm Apache Struts RCE Vulnerability | High Known exploited | Also affects org.apache.struts:struts2-core |
| GHSA-47qp-8v9g-39hp Code injection in Apache Struts | Critical Known exploited | Also affects org.apache.struts:struts2-core |
| GHSA-4wrr-9h5r-m92w Apache Struts Remote Java Code Execution | Critical Known exploited | Also affects org.apache.struts:struts2-core |
| CVE-2020-17530 Remote code execution in Apache Struts | Critical Known exploited | Also affects org.apache.struts:struts2-core |
| GHSA-j77q-2qqg-6989 Apache Struts vulnerable to remote arbitrary command execution due to improper input validation | Critical Known exploited | Also affects org.apache.struts:struts2-core |
| CVE-2018-11776 Apache Struts vulnerable to remote command execution (RCE) due to improper input validation | High Known exploited | Also affects org.apache.struts:struts2-core |
| GHSA-qcfc-hmrc-59x7 Apache Struts 2 is Missing XML Validation | High | Also affects org.apache.struts:struts2-core |
| GHSA-rg58-xhh7-mqjw Apache Struts has a Denial of Service vulnerability | High | Also affects org.apache.struts:struts2-core |
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