dbcve.org
3cdaemonApplication · 3com

CVE-2005-0275

MEDIUM · 5.0 CVSS v2.0 Published 2005-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
TFTP in 3Com 3CDaemon 2.0 revision 10 allows remote attackers to cause a denial of service (application crash) via a GET request containing an MS-DOS device name.

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 confidence

The TFTP server component in 3Com 3CDaemon 2.0 revision 10 crashes when processing a GET request containing an MS-DOS device name (such as CON, PRN, AUX, NUL, COM1, LPT1). This causes a denial of service condition, rendering the TFTP service unavailable.

MitigationSince this is a 2005 vulnerability in likely end-of-life software, apply compensating controls: restrict network access to the TFTP service to trusted internal systems only, or migrate to a supported TFTP server solution if the product is no longer maintained.

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
3cdaemonApplication
Affected:= 2.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm 3CDaemon is installed
    Check running processes or installed programs for 3CDaemon or 3cdaemon
    Affected if The software is present on the system
  2. Identify the installed version
    Use the software's built-in version check, typically via '3CDaemon -v' or check the executable properties/version information
    Affected if The version is exactly 2.0 (the only affected version listed)
  3. Verify TFTP server is enabled
    Check the 3CDaemon configuration to confirm the TFTP server component is active and listening
    Affected if TFTP server is enabled and the service is running
  4. Check network exposure
    Determine if the TFTP service is bound to network-accessible interfaces or exposed to untrusted networks
    Affected if The TFTP port (typically UDP 69) is accessible from networks beyond trusted internal systems

You are affected if 3CDaemon version 2.0 is installed with the TFTP server component enabled and exposed to any network where an attacker could send a specially crafted GET request containing an MS-DOS device name.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since this is a 2005 vulnerability in likely end-of-life software, apply compensating controls: restrict network access to the TFTP service to trusted internal systems only, or migrate to a supported TFTP server solution if the product is no longer maintained.

Fix this in 3cdaemon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-0275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-0275 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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