CVE-2004-0794
published 2004-10-20CVE-2004-0794: Multiple signal handler race conditions in lukemftpd (aka tnftpd before 20040810) allow remote authenticated attackers to cause a denial of service or execute…
PriorityP420medium5.1CVSS 2.0
AVNACHAuNCPIPAP
EPSS
2.42%
82.2th percentile
Multiple signal handler race conditions in lukemftpd (aka tnftpd before 20040810) allow remote authenticated attackers to cause a denial of service or execute arbitrary code.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| luke_mewburn | lukemftp | — | — |
| luke_mewburn | lukemftp | — | — |
| luke_mewburn | tnftpd | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Signal Handler Race Condition
mitre_cwe
CWE-364 Signal Handler Race Condition
CWE-364: Signal Handler Race Condition
The product uses a signal handler that introduces a race condition.
Race conditions frequently occur in signal handlers, since signal handlers support asynchronous actions. These race conditions have a variety of root causes and symptoms. Attackers may be able to exploit a signal handler race condition to cause the product state to be corrupted, possibly leading to a denial of service or even code execution. These issues occur when non-reentrant functions, or state-sensitive actions occur in the signal handler, where they may be called at any time. These behaviors can violate assumptions being made by the "regular" code that is interrupted, or by other signal handlers that may also be invoked. If these functions are called at an inopportune moment -
CWE
Signal Handler with Functionality that is not Asynchronous-Safe
mitre_cwe
CWE-828 Signal Handler with Functionality that is not Asynchronous-Safe
CWE-828: Signal Handler with Functionality that is not Asynchronous-Safe
The product defines a signal handler that contains code sequences that are not asynchronous-safe, i.e., the functionality is not reentrant, or it can be interrupted.
This can lead to an unexpected system state with a variety of potential consequences depending on context, including denial of service and code execution. Signal handlers are typically intended to interrupt normal functionality of a program, or even other signals, in order to notify the process of an event. When a signal handler uses global or static variables, or invokes functions that ultimately depend on such state or its associated metadata, then it could corrupt system state that is being used by normal functionality. This could subject the program
ftp://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2004-009.txt.aschttp://lists.grok.org.uk/pipermail/full-disclosure/2004-August/025418.htmlhttp://www.debian.org/security/2004/dsa-551http://www.vuxml.org/freebsd/c4b025bb-f05d-11d8-9837-000c41e2cdad.htmlhttps://exchange.xforce.ibmcloud.com/vulnerabilities/17020ftp://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2004-009.txt.aschttp://lists.grok.org.uk/pipermail/full-disclosure/2004-August/025418.htmlhttp://www.debian.org/security/2004/dsa-551http://www.vuxml.org/freebsd/c4b025bb-f05d-11d8-9837-000c41e2cdad.htmlhttps://exchange.xforce.ibmcloud.com/vulnerabilities/17020
2004-10-20
Published