dbcve.org
StrutsFramework / library · Apache

CVE-2023-34396

HIGH · 7.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 2.5.31 / 6.1.2.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Allocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2. Upgrade to Struts 2.5.31 or 6.1.2.1 or greater

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 · high confidence

A resource exhaustion vulnerability in Apache Struts allows attackers to cause denial of service by allocating resources without proper limits or throttling. The vulnerability affects Struts versions 2.x through 2.5.30 and 6.x through 6.1.2, where insufficient controls on resource allocation can be exploited to exhaust server resources.

MitigationUpgrade Apache Struts to version 2.5.31 or 6.1.2.1 or greater to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.5.31>= 6.0.0, < 6.1.2.1

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
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Apache Struts installation
    Identify if your application uses Apache Struts by examining the web application directory, WAR file contents, or application dependencies (pom.xml, lib folder). Look for struts2-core.jar or struts-core.jar files.
    Affected if Apache Struts libraries are present in the application
  2. Determine installed Struts version
    Check the version of the Struts jar file in your application (e.g., struts2-core-x.x.x.jar). Also check application startup logs which typically display the Struts version at initialization.
    Affected if Version cannot be determined or is not visible
  3. Compare version against affected ranges
    If your version is 2.x, ensure it is 2.5.31 or higher. If your version is 6.x, ensure it is 6.1.2.1 or higher. Any version below 2.5.31 (starting from 2.0.0) or between 6.0.0 and 6.1.2 is vulnerable.
    Affected if Version is < 2.5.31 for 2.x branch OR version is >= 6.0.0 and < 6.1.2.1 for 6.x branch
  4. Verify resource consumption behavior
    Monitor server resource usage (CPU, memory, network connections) during normal application operation. This vulnerability allows unbounded resource allocation, so unusually high or growing resource consumption may indicate exploitation attempts.
    Affected if Unbounded resource allocation is observed without rate limiting in place

A system is affected if it runs any Apache Struts version below 2.5.31 (2.x branch) or between 6.0.0 and 6.1.2.1 (6.x branch).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 2.5.31 / 6.1.2.1 or later
Fixed in 2.5.316.1.2.1
Interim mitigation

Upgrade Apache Struts to version 2.5.31 or 6.1.2.1 or greater to remediate this vulnerability.

Recommended fix High confidence

Struts 2.5.31 or Struts 6.1.2.1 (depending on major version line)

  1. Identify the current Struts version in use by checking pom.xml, WAR file manifest, or application dependencies
  2. For Struts 2.x users: Update the Struts dependency version in pom.xml or build configuration from any version < 2.5.31 to 2.5.31
  3. For Struts 6.x users: Update the Struts dependency version in pom.xml or build configuration from any version < 6.1.2.1 to 6.1.2.1
  4. Rebuild the application with the updated dependency
  5. Run existing tests to verify application functionality after the upgrade
  6. Deploy the rebuilt application
Caveat Review release notes for any behavior changes between your current version and the target version; minor version upgrades typically have low risk

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

Fix this in Struts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34396 — 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-2023-34396 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