CVE-2005-3124
First published: Sun Nov 06 2005(Updated: )
syslogtocern in Acme thttpd before 2.23 allows local users to write arbitrary files via a symlink attack on a temporary file.
Credit: security@debian.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Acme Labs thttpd | =2.21b | |
| Acme Labs thttpd | =2.23b1 |
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-3124?
CVE-2005-3124 is considered a moderate severity vulnerability due to its potential impact on local user permissions.
How do I fix CVE-2005-3124?
To fix CVE-2005-3124, upgrade to a version of thttpd later than 2.23b1 that addresses the symlink vulnerability.
What are the risks associated with CVE-2005-3124?
The risks of CVE-2005-3124 include unauthorized file writes by local users, potentially leading to data corruption or privilege escalation.
Who is affected by CVE-2005-3124?
CVE-2005-3124 affects users running Acme thttpd versions 2.21b and 2.23b1.
What kind of attack does CVE-2005-3124 involve?
CVE-2005-3124 involves a symlink attack that allows local users to exploit temporary files to write arbitrary data.
- collector/nvd-historical
- collector/nvd-index
- agent/softwarecombine
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/severity
- agent/remedy
- agent/author
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/acme labs
- canonical/acme labs thttpd
- version/acme labs thttpd/2.21b
- version/acme labs thttpd/2.23b1