dbcve.org
StrutsFramework / library · Apache

CVE-2019-0230

CRITICAL · 9.8 CVSS v3.1 Published 2020-09-14
Fix available
A fix is available. Upgrade to after 8.0.23 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StrutsFramework / library
Affected:>= 2.0.0, <= 2.5.20
Communications Policy ManagementApplication
Affected:= 12.5.0
Financial Services Data Integration HubApplication
Affected:= 8.0.3= 8.0.6
Financial Services Market Risk Measurement And ManagementApplication
Affected:= 8.0.6
Mysql Enterprise MonitorDatabase / datastore
Affected:<= 8.0.23

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.23
Vendor patch www.oracle.com →
Recommended fix High confidence

Apache Struts 2.5.22 or later; Oracle products require April 2021 CPU; MySQL Enterprise Monitor 8.0.24+

  1. 1. Identify all applications and systems using Apache Struts 2.x libraries within your environment
  2. 2. For direct Apache Struts installations: Upgrade to Struts 2.5.22 or later (the first version containing the security fix)
  3. 3. For Oracle Communications Policy Management 12.5.0: Apply Oracle Critical Patch Update April 2021 (or later) from https://www.oracle.com/security-alerts/cpuApr2021.html
  4. 4. For Oracle Financial Services Data Integration Hub 8.0.3/8.0.6: Apply Oracle Critical Patch Update April 2021
  5. 5. For Oracle Financial Services Market Risk Measurement And Management 8.0.6: Apply Oracle Critical Patch Update April 2021
  6. 6. For MySQL Enterprise Monitor <=8.0.23: Upgrade to version 8.0.24 or later which contains the patched Struts library
  7. 7. Rebuild and redeploy any applications that bundle the vulnerable Struts library
  8. 8. Verify the upgrade by checking the Struts version in deployed artifacts (typically in WEB-INF/lib/struts-core*.jar)
Caveat Review release notes for Struts 2.5.x series for breaking changes between your current version and 2.5.22; Oracle product patches may require downtime and regression testing

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0230 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data