dbcve.org
StrutsFramework / library · Apache

CVE-2023-34149

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 · moderate confidence

A resource allocation vulnerability in Apache Struts allows attackers to cause denial of service through excessive resource consumption due to lack of proper limits or throttling during request processing. This affects Struts versions 2.5.30 and earlier and 6.1.2 and earlier.

MitigationUpgrade to Struts 2.5.31 or 6.1.2.1 or greater to implement proper resource limits and prevent resource exhaustion attacks.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Apache Struts installation
    Locate struts2-core JAR files in the application deployment directory, WEB-INF/lib folder, or classpath. Check for struts.xml configuration files in the application or classpath.
    Affected if No Struts JAR or configuration files are found, meaning Apache Struts is not in use.
  2. Determine installed Struts version
    Examine the struts2-core JAR filename for the version number (e.g., struts2-core-2.5.30.jar). Alternatively, inspect the MANIFEST.MF file inside the JAR for the Implementation-Version attribute.
    Affected if The version cannot be determined or the JAR is not present.
  3. Compare version against affected ranges
    If a version is found, compare it to the affected ranges: Struts 2.5.30 and earlier (versions less than 2.5.31) OR Struts 6.0.0 through 6.1.2 (versions less than 6.1.2.1).
    Affected if The installed version falls within < 2.5.31 OR >= 6.0.0 and < 6.1.2.1.
  4. Verify active request processing
    Confirm the application processes incoming HTTP requests through Struts action mappings. Check if the application exposes web endpoints that use Struts actions or conventions.
    Affected if The application runs and processes requests through Struts, making the resource exhaustion vulnerability accessible.

A user is affected if their application runs any version of Apache Struts 2.5.30 or earlier, or version 6.0.0 through 6.1.2, and processes HTTP requests through the Struts framework.

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 to Struts 2.5.31 or 6.1.2.1 or greater to implement proper resource limits and prevent resource exhaustion attacks.

Recommended fix High confidence

Struts 2.5.31 or 6.1.2.1

  1. Identify the current Struts version in use by checking project dependencies (pom.xml, build.gradle, or library manifests)
  2. Stop the application or service using Struts
  3. Update the Struts dependency to version 2.5.31 for Struts 2.x projects, or 6.1.2.1 for Struts 6.x projects
  4. For Maven projects, update the struts2-core dependency version in pom.xml: <version>2.5.31</version> or <version>6.1.2.1</version>
  5. For Gradle projects, update: implementation 'org.apache.struts:struts2-core:2.5.31' or 'org.apache.struts:struts2-core:6.1.2.1'
  6. Rebuild the application to verify dependency compatibility
  7. Redeploy the updated application
  8. Restart the application
Caveat Minimal risk - patch releases within same major version typically contain only bug fixes and security patches

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

Fix this in Struts Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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