CVE-2007-4004
published 2007-07-26CVE-2007-4004: Buffer overflow in the ftp client in IBM AIX 5.3 SP6 and 5.2.0 allows local users to execute arbitrary code via unspecified vectors that trigger the overflow…
PriorityP428medium6.9CVSS 2.0
AVLACMAuNCCICAC
EXPLOIT
EPSS
0.85%
54.4th percentile
Buffer overflow in the ftp client in IBM AIX 5.3 SP6 and 5.2.0 allows local users to execute arbitrary code via unspecified vectors that trigger the overflow in a gets function call. NOTE: the client is setuid root on AIX, so this issue crosses privilege boundaries.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| ibm | aix | — | — |
| ibm | aix | — | — |
CVEs like this are exactly what “Exploited This Week” covers.
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 writeups or analysis indexed.
CWE
Use of Prohibited Code
mitre_cwe
CWE-1177 Use of Prohibited Code
CWE-1177: Use of Prohibited Code
The product uses a function, library, or third party component
that has been explicitly prohibited, whether by the developer or
the customer.
The developer - or customers - may wish to restrict or eliminate use of a function, library, or third party component for any number of reasons, including real or suspected vulnerabilities; difficulty to use securely; export controls or license requirements; obsolete or poorly-maintained code; internal code being scheduled for deprecation; etc. To reduce risk of vulnerabilities, the developer might maintain a list of "banned" functions that programmers must avoid using because the functions are difficult or impossible to use securely. This issue can also make the product more costly and difficult to maintain.
Modes
CWE
Use of Inherently Dangerous Function
mitre_cwe
CWE-242 Use of Inherently Dangerous Function
CWE-242: Use of Inherently Dangerous Function
The product calls a function that can never be guaranteed to work safely.
Certain functions behave in dangerous ways regardless of how they are used. Functions in this category were often implemented without taking security concerns into account. The gets() function is unsafe because it does not perform bounds checking on the size of its input. An attacker can easily send arbitrarily-sized input to gets() and overflow the destination buffer. Similarly, the >> operator is unsafe to use when reading into a statically-allocated character array because it does not perform bounds checking on the size of its input. An attacker can easily send arbitrarily-sized input to the >> operator and overflow the destination buffer.
Modes of Introduction:
Pha
ftp://aix.software.ibm.com/aix/efixes/security/READMEhttp://labs.idefense.com/intelligence/vulnerabilities/display.php?id=571http://secunia.com/advisories/26219http://www-1.ibm.com/support/docview.wss?uid=isg1IZ01812http://www-1.ibm.com/support/docview.wss?uid=isg1IZ01813http://www.securityfocus.com/bid/25077http://www.securitytracker.com/id?1018465http://www.vupen.com/english/advisories/2007/2675https://exchange.xforce.ibmcloud.com/vulnerabilities/35627ftp://aix.software.ibm.com/aix/efixes/security/READMEhttp://labs.idefense.com/intelligence/vulnerabilities/display.php?id=571http://secunia.com/advisories/26219http://www-1.ibm.com/support/docview.wss?uid=isg1IZ01812http://www-1.ibm.com/support/docview.wss?uid=isg1IZ01813http://www.securityfocus.com/bid/25077http://www.securitytracker.com/id?1018465http://www.vupen.com/english/advisories/2007/2675https://exchange.xforce.ibmcloud.com/vulnerabilities/35627
2007-07-26
Published