CVE-2005-0275
First published: Thu Feb 10 2005(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| 3Com 3CDaemon | =2.0-revision_10 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2005-0275?
CVE-2005-0275 is classified as a denial of service vulnerability.
How do I fix CVE-2005-0275?
To mitigate CVE-2005-0275, consider upgrading from 3Com 3CDaemon 2.0 revision 10 to a more secure version or disable TFTP services.
What causes the vulnerability in CVE-2005-0275?
CVE-2005-0275 is caused by the handling of GET requests containing MS-DOS device names, which leads to application crashes.
Which version of 3Com 3CDaemon is affected by CVE-2005-0275?
CVE-2005-0275 specifically affects 3Com 3CDaemon version 2.0 revision 10.
Can CVE-2005-0275 be exploited remotely?
Yes, CVE-2005-0275 can be exploited remotely, allowing attackers to cause a denial of service.
- collector/nvd-historical
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/severity
- agent/description
- agent/first-publish-date
- agent/tags
- agent/event
- agent/source
- vendor/3com
- canonical/3com 3cdaemon
- version/3com 3cdaemon/2.0-revision_10