CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in Apache Struts. In CISA KEV since 2021-11-03, with known ransomware use. EPSS >99.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.struts:struts2-core 2.3.32, 2.5.10.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Horg.apache.struts:struts2-core (Maven): fixed in 2.3.32, 2.5.10.1Explain CVE-2017-5638 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-5638?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-5638?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-5638 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| apache:struts | from 2.2.3 before 2.3.32 |
| apache:struts | from 2.5.0 before 2.5.10.1 |
| ibm:storwize_v3500_firmware | 7.7.1.6 |
| ibm:storwize_v3500_firmware | 7.8.1.0 |
| ibm:storwize_v5000_firmware | 7.7.1.6 |
| ibm:storwize_v5000_firmware | 7.8.1.0 |
| ibm:storwize_v7000_firmware | 7.7.1.6 |
| ibm:storwize_v7000_firmware | 7.8.1.0 |
| lenovo:storage_v5030_firmware | 7.7.1.6 |
| lenovo:storage_v5030_firmware | 7.8.1.0 |
| hp:server_automation | 9.1.0 |
| hp:server_automation | 10.0.0 |
| hp:server_automation | 10.1.0 |
| hp:server_automation | 10.2.0 |
| hp:server_automation | 10.5.0 |
| oracle:weblogic_server | 10.3.6.0.0 |
| oracle:weblogic_server | 12.1.3.0.0 |
| oracle:weblogic_server | 12.2.1.1.0 |
| oracle:weblogic_server | 12.2.1.2.0 |
| arubanetworks:clearpass_policy_manager | before 6.6.5 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-j77q-2qqg-6989 | Maven | org.apache.struts:struts2-core | >=2.3.0 <2.3.32 | 2.3.32 |
| GHSA-j77q-2qqg-6989 | Maven | org.apache.struts:struts2-core | >=2.5.0 <2.5.10.1 | 2.5.10.1 |
Red Hat rates this Critical.
A previous statement by Red Hat related to this CVE, prior to August 2019, said that Apache Struts 2 is not included in any Red Hat products. This earlier statement was incorrect. While Struts 2 is not actively compiled, shipped, used, or enabled in any Red Hat provided final products, and does not cause any vulnerability in the product, struts2-core jars have been included in some products' source code packages. The inclusion was part of an import of the Google Guice repository, which includes struts2-core. Customers that build artefacts from our source code could be at risk. Red Hat will remove these artefacts from source code in future releases.
The products that included the Struts 2 artefacts in their source jars:
Fuse Service Works 6.0.0
Single Sign On 7.3.0+
If you have used the source package from one of these products to build artefacts on your system, you should do the following to remove potentially affected jars:
1. Run 'find . -name struts2*.jar' under the source location
2. Remove any files found
This will not affect the product, as the jar is included with the source of google-guice, but no functionality requiring struts2 is implemented.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat JBoss Fuse Service Works 6 | struts2-core | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-5638.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.