CVE-2023-42657
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 · uneditedIn WS_FTP Server versions prior to 8.7.4 and 8.8.2, a directory traversal vulnerability was discovered. An attacker could leverage this vulnerability to perform file operations (delete, rename, rmdir, mkdir) on files and folders outside of their authorized WS_FTP folder path. Attackers could also escape the context of the WS_FTP Server file structure and perform the same level of operations (delete, rename, rmdir, mkdir) on file and folder locations on the underlying operating system.
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 WS_FTP Server versions prior to 8.7.4 and 8.8.2 allows authenticated or unauthenticated attackers to escape the authorized FTP folder path and perform file operations (delete, rename, rmdir, mkdir) directly on the underlying operating system's file structure.
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< 8.7.4>= 8.8.0, < 8.8.2CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 WS_FTP Server versionLocate the WS_FTP Server installation and check its version number. This is typically visible in the software itself, Windows Programs and Features, or the About section of the WS_FTP Server administration interface.Affected if The installed version is any version prior to 8.7.4, or any version from 8.8.0 up to but not including 8.8.2.
-
Confirm the FTP service is runningVerify that the WS_FTP Server service is actively running and accepting connections. The vulnerability can be exploited if the FTP service is exposed, even if no user sessions are active.Affected if The WS_FTP Server FTP service is running and network-accessible.
-
Check for external FTP access exposureDetermine whether the WS_FTP Server is exposed to external or untrusted networks. This includes checking firewall rules, NAT configurations, or any port forwarding that allows external access to FTP ports (typically port 21 or configured alternative ports).Affected if The FTP service is reachable from untrusted networks or the internet without proper network segmentation.
-
Review user access controlsExamine the configured FTP user accounts and their permitted root directories. The vulnerability allows escaping the authorized folder path, so any configuration that restricts users to specific directories would be affected if the traversal is possible.Affected if FTP users are configured with restricted home directories or chroot jails.
A user is affected if WS_FTP Server version is less than 8.7.4, or between 8.8.0 and 8.8.1 (inclusive), and the FTP service is running and accessible.
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 · scoped8.7.48.8.2
Upgrade WS_FTP Server to version 8.7.4 or 8.8.2 or later to remediate this vulnerability.
WS_FTP Server 8.7.4 or 8.8.2 (or latest stable release)
- Backup the current WS_FTP Server configuration and data
- Stop the WS_FTP Server service
- Download the fixed version (8.7.4 or 8.8.2) from the Progress Software customer portal at www.progress.com or community.progress.com
- Install the upgrade following standard WS_FTP Server upgrade procedures
- Verify the installed version matches the expected fixed version
- Restart the WS_FTP Server service
- Test to confirm the directory traversal vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing5.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 $3,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42657 — 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-2023-42657 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