Sun Solaris acl(2) system call denial of service
| solaris-acl-system-dos (34147) |  Low Risk |
Description:
Sun Solaris is vulnerable to a denial of service, caused by an integer signedness error in the acl(2) system call. By sending a specially-crafted argument that leads to a large amount of memory allocation, a local attacker could exploit this vulnerability to cause a system panic.
Platforms Affected:
- Sun, Solaris 10
- Sun, Solaris 10 x86
- Sun, Solaris 10 SPARC
Remedy:
Refer to Sun Alert ID: 102869 for patch or upgrade information. See References.
Consequences:
Denial of Service
References:
- iDefense Labs PUBLIC ADVISORY: 05.07.07, Sun Microsystems Solaris ACE_SETACL Integer Signedness DoS Vulnerability at http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=524.
- Sun Alert ID: 102869, Security Vulnerability Relating to the acl(2) System Call May Allow Denial of Service (DoS) to the System at http://sunsolve.sun.com/search/document.do?assetkey=1-26-102869-1.
- ASA-2007-243: Security Vulnerability Relating to the acl(2) System Call May Allow Denial of Service (DoS) to the System (Sun 102869)
- BID-23863: Sun Solaris ACE_SETACL Local Denial Of Service Vulnerability
- CVE-2007-2529: Integer signedness error in the acl (facl) system call in Solaris 10 before 20070507 allows local users to cause a denial of service (kernel panic) and possibly gain privileges via a certain argument, related to ACE_SETACL.
- SA25162: Sun Solaris "acl()" Local Denial of Service
- SECTRACK ID: 1018009: Solaris facl() Integer Error Lets Local Users Deny Service
- VUPEN/ADV-2007-1683: Sun Solaris acl System Call Argument Handling Local Denial of Service Vulnerability
Reported:
May 07, 2007
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net