GNU Chess Local Buffer Overflow Vulnerability
BID:8097
Info
GNU Chess Local Buffer Overflow Vulnerability
| Bugtraq ID: | 8097 |
| Class: | Boundary Condition Error |
| CVE: | |
| Remote: | No |
| Local: | Yes |
| Published: | Jul 03 2003 12:00AM |
| Updated: | Jul 03 2003 12:00AM |
| Credit: | Discovery of this vulnerability credited to t0asty [ [email protected] ]. |
| Vulnerable: |
GNU Chess 5.0 6 GNU Chess 5.0 5 GNU Chess 5.0 3beta GNU Chess 5.0 2 |
| Not Vulnerable: | |
Discussion
GNU Chess Local Buffer Overflow Vulnerability
A local buffer overflow has been reported for GNU Chess that may result in an attacker obtaining elevated privileges.
The vulnerability exists due to insufficient boundary checks performed on some commandline options.
Successful exploitation may result in the execution of attacker-supplied code. To be exploited for elevated privileges, the software must be setuid or setgid. Since GNU Chess is used as a back-end for some chess-related software, a situation could arise where it is invoked with user-supplied arguments by another program.
A local buffer overflow has been reported for GNU Chess that may result in an attacker obtaining elevated privileges.
The vulnerability exists due to insufficient boundary checks performed on some commandline options.
Successful exploitation may result in the execution of attacker-supplied code. To be exploited for elevated privileges, the software must be setuid or setgid. Since GNU Chess is used as a back-end for some chess-related software, a situation could arise where it is invoked with user-supplied arguments by another program.
Exploit / POC
GNU Chess Local Buffer Overflow Vulnerability
The following exploit was provided:
The following exploit was provided:
Solution / Fix
GNU Chess Local Buffer Overflow Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.