StrutsFramework / library · Apache
CVE-2024-53677
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 · uneditedFile upload logic in Apache Struts is flawed. An attacker can manipulate file upload params to enable paths traversal and under some circumstances this can lead to uploading a malicious file which can be used to perform Remote Code Execution. This issue affects Apache Struts: from 2.0.0 before 6.4.0. Users are recommended to upgrade to version 6.4.0 at least and migrate to the new file upload mechanism https://struts.apache.org/core-developers/file-upload . If you are not using an old file upload logic based on FileuploadInterceptor your application is safe. You can find more details in https://cwiki.apache.org/confluence/display/WW/S2-067
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 confidenceApache Struts contains a path traversal vulnerability in its legacy file upload logic (FileuploadInterceptor) that allows attackers to manipulate file upload parameters to write malicious files to arbitrary locations on the server, potentially achieving remote code execution.
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
>= 2.0.0, < 6.4.0CVSS 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
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Struts versionInspect the Struts library JAR file in your application's classpath (typically in WEB-INF/lib/) or check your dependency management file (pom.xml, build.gradle). Look for a JAR named struts2-core-{version}.jar and note the version number.Affected if The installed version is 2.0.0 or higher but below 6.4.0
-
Locate Struts configuration filesSearch for struts.xml (primary) or struts-config.xml (legacy) files in your application's configuration directories, typically under WEB-INF/classes/ or src/main/resources/ in the deployment.Affected if No Struts configuration files exist - the application may not be using Struts
-
Check for FileuploadInterceptor configurationOpen the struts.xml or struts-config.xml file and search for 'FileuploadInterceptor' or 'fileUpload' in the interceptor configurations. Also check action definitions that reference this interceptor.Affected if FileuploadInterceptor is explicitly defined or referenced in any action configuration - the vulnerable legacy upload mechanism is enabled
-
Inspect action mappings for file upload usageIn struts.xml, review all <action> elements and their associated <interceptor-ref> tags. Look for actions that handle multipart/form-data file uploads and which interceptor stack they use.Affected if Any action explicitly uses FileuploadInterceptor or a stack containing FileuploadInterceptor for file uploads
-
Check for deprecated upload mechanismsSearch configuration for 'struts.multipart.parser' settings or references to Jakarta Stream multipart parser versus the new standard. Also check for any custom interceptor stacks that bypass the newer upload mechanisms.Affected if The application uses the legacy Jakarta Stream multipart parser or lacks explicit configuration of the newer upload mechanism (post-6.4.0 default)
A user is affected if they have Apache Struts version 2.0.0 through 6.3.x with FileuploadInterceptor enabled in their Struts configuration for any action handling file uploads.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.4.0
Upgrade to Apache Struts 6.4.0 or later and migrate to the new file upload mechanism; if FileuploadInterceptor is not in use, the application is not vulnerable.
6.4.0
- 1. Identify all Struts dependencies in your project (check pom.xml, build.gradle, or lib directories)
- 2. Update Struts version to 6.4.0 in your dependency management
- 3. Review application code for usage of FileuploadInterceptor or old file upload logic
- 4. If using old file upload mechanism, migrate to the new file upload mechanism as documented at https://struts.apache.org/core-developers/file-upload
- 5. Rebuild the application with the updated dependencies
- 6. Test file upload functionality to ensure proper operation after migration
- 7. Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Struts
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53677 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-53677 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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