CVE-2024-25153
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 · uneditedA directory traversal within the ‘ftpservlet’ of the FileCatalyst Workflow Web Portal allows files to be uploaded outside of the intended ‘uploadtemp’ directory with a specially crafted POST request. In situations where a file is successfully uploaded to web portal’s DocumentRoot, specially crafted JSP files could be used to execute code, including web shells.
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 confidenceA directory traversal vulnerability in the ftpservlet of FileCatalyst Workflow Web Portal allows attackers to escape the intended uploadtemp directory via specially crafted POST requests. When files are uploaded to the web portal's DocumentRoot, malicious JSP files can be placed and executed for remote code execution, including web shells.
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>= 5.0, < 5.1.6= 5.1.6CVSS 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 FileCatalyst Workflow versionLocate the installation directory and check version info in release notes, manifest, or admin interface. Common paths: /opt/filecatalyst, C:\Program Files\FileCatalyst, or check the WAR file version inside the deployed webapp.Affected if Installed version is 5.0 through 5.1.5 inclusive, or exactly 5.1.6 (version >= 5.0 AND < 5.1.6, OR version = 5.1.6)
-
Verify ftpservlet is exposedCheck if the ftpservlet endpoint is accessible on the web server. Inspect web.xml or the deployed application's URL patterns for /ftpservlet or similar paths. Attempt a HEAD request to the endpoint if authorized.Affected if The ftpservlet is deployed and reachable via HTTP/HTTPS on the web portal
-
Confirm upload functionality is enabledCheck the application configuration for uploadtemp directory settings. Look for uploadtemp path in config files (e.g., server.properties, web.xml init-params, or application.yml). Verify the ftpservlet has file upload processing enabled.Affected if Upload functionality is enabled and the uploadtemp directory is in use for handling POST requests
-
Inspect JSP execution policy in upload directoriesReview web server configuration (Tomcat web.xml, IIS URL authorization, or equivalent) for JSP servlet mappings. Check if JSP files can execute in the DocumentRoot or any user-upload directories. Look for servlet mappings like <url-pattern>*.jsp</url-pattern> and their associated servlet definitions.Affected if JSP execution is permitted in DocumentRoot or in directories where uploaded files are stored
-
Check DocumentRoot writabilityVerify the web server DocumentRoot directory permissions. Confirm the application has write access to store files there. Inspect the ftpservlet configuration to determine if files can be written outside the intended uploadtemp directory.Affected if DocumentRoot or any upload-accessible directory is writable by the application process
You are affected if your FileCatalyst Workflow version falls within 5.0 to 5.1.5 or is exactly 5.1.6, AND the ftpservlet is active with upload functionality, AND JSP execution is allowed in accessible upload directories.
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 · scoped5.1.6
Apply vendor patch or update to a fixed version that implements proper path validation and sanitization in the ftpservlet upload functionality. Additionally, configure the web server to prevent JSP execution in all upload directories.
FileCatalyst Workflow 5.1.7 or later
- 1. Review the current FileCatalyst Workflow installation to confirm the exact version installed (check application web interface or deployment documentation)
- 2. Schedule a maintenance window for the upgrade process
- 3. Back up the current FileCatalyst Workflow installation, including configuration files, database (if applicable), and any custom settings
- 4. Download FileCatalyst Workflow version 5.1.7 or later from the official Fortra/FileCatalyst download portal (filecatalyst.software or www.fortra.com)
- 5. Deploy the upgraded version following the standard FileCatalyst installation/upgrade documentation
- 6. Verify the ftpservlet is functioning correctly after upgrade
- 7. Test that file uploads are now restricted to the intended uploadtemp directory
- 8. Confirm no custom configurations or integrations have been broken by the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25153 — 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-25153 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