CVE-2005-0276
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 · uneditedMultiple format string vulnerabilities in the FTP service in 3Com 3CDaemon 2.0 revision 10 allow remote attackers to cause a denial of service (application crash) via format string specifiers in (1) the username, (2) cd, (3) delete, (4) rename, (5) rmdir, (6) literal, (7) stat, or (8) CWD 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 · high confidenceMultiple format string vulnerabilities exist in the FTP service of 3Com 3CDaemon 2.0 revision 10. Remote attackers can inject format string specifiers into various FTP commands (username, cd, delete, rename, rmdir, literal, stat, CWD) causing the application to crash and resulting in a denial of service.
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= 2.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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 3CDaemon is installedSearch for the 3CDaemon executable or service on the system. Check Program Files directory, system services, or running processes for '3cdaemon' or '3CDaemon'.Affected if 3CDaemon executable or service is found on the system
-
Verify the installed version is 2.0Check the version of the 3CDaemon installation. Right-click the executable, select Properties, and view the Version tab. Alternatively, run '3cdaemon -v' or check the service details if available.Affected if The installed version is 3CDaemon 2.0 (specifically revision 10)
-
Confirm FTP service is enabledCheck if the FTP service in 3CDaemon is running or configured to start. Look for the service status in Windows Services or check if port 21 is listening.Affected if The FTP service is running and accepting connections on port 21
-
Test for format string vulnerabilityConnect to the FTP service and issue format string commands. Try commands like 'USER %s%s%s' or 'CWD %n%n%n' and observe if the server crashes or produces abnormal output.Affected if The server crashes, hangs, or displays unexpected format string output in response to format specifiers in FTP commands
A system is affected if 3CDaemon version 2.0 is installed with the FTP service running, as the exact version matches the affected range and the vulnerable FTP commands are available.
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 dataUpdate 3CDaemon to the latest version if a patched release exists, or migrate to a supported FTP server implementation. If neither is feasible, restrict network access to the FTP service using firewall rules or disable the service until a replacement is deployed.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0276 — 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-2005-0276 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