CVE-2012-4729
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 · uneditedWing FTP Server before 4.1.1 allows remote authenticated users to cause a denial of service (daemon crash) via two zip commands.
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 confidenceWing FTP Server versions prior to 4.1.1 contain a denial of service vulnerability where remote authenticated users can crash the daemon by issuing two specific zip commands. The vulnerability is exploitable remotely but requires valid credentials, and results in the FTP service becoming unavailable.
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<= 4.0.9= 1.1= 1.2= 1.3= 1.4= 1.5= 1.6= 2.0= 2.1= 2.3= 2.4= 3.0.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
- Authentication
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/C:N/I:N/A:C
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.
-
Confirm Wing FTP Server is runningCheck running processes or services for Wing FTP Server executable (wingftpd.exe on Windows, or wingftpdaemon on Linux). On Windows, also check installed programs list.Affected if Wing FTP Server is installed and running on the system
-
Identify installed versionCheck the About dialog within the Wing FTP Server administration console, or locate the version in the server's installation directory/readme files.Affected if Version cannot be determined or is <= 4.0.9, or falls within 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 2.0, 2.1, 2.3, 2.4, or 3.0.0
-
Verify FTP service is exposed remotelyConfirm the FTP service port (default 21) is open to network access and listening on the server. Check firewall rules and server binding configuration.Affected if FTP port is accessible from untrusted networks or the internet
-
Confirm valid user accounts existReview user accounts configured in Wing FTP Server administration console. Check if any accounts have FTP access permissions enabled.Affected if At least one valid FTP user account exists with login capability
System is affected if Wing FTP Server version is <= 4.0.9 or matches any affected 1.x/2.x/3.x version listed, AND the FTP service is accessible remotely with valid user credentials, since the DoS triggers via authenticated zip commands.
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.
From vendor dataUpgrade Wing FTP Server to version 4.1.1 or later to remediate this vulnerability. As an authenticated-user DoS with no public exploit details, priority should be balanced against other infrastructure patching cycles.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4729 — 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-2012-4729 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