Linux Kernel Trojan Horse Vulnerability
BID:8987
Info
Linux Kernel Trojan Horse Vulnerability
| Bugtraq ID: | 8987 |
| Class: | Unknown |
| CVE: | |
| Remote: | No |
| Local: | Yes |
| Published: | Nov 05 2003 12:00AM |
| Updated: | Nov 05 2003 12:00AM |
| Credit: | Discovery of this vulnerability has been credited to Larry McVoy ([email protected]). |
| Vulnerable: |
Linux kernel 2.6 -test9-CVS |
| Not Vulnerable: | |
Discussion
Linux Kernel Trojan Horse Vulnerability
It has been announced that a file was modified on the kernel.bkbits.net Linux Kernel CVS tree by a malicious party. The file in question was modified to include trojan horse code that would potentially allow a local user to elevate privileges.
It has been announced that a file was modified on the kernel.bkbits.net Linux Kernel CVS tree by a malicious party. The file in question was modified to include trojan horse code that would potentially allow a local user to elevate privileges.
Exploit / POC
Linux Kernel Trojan Horse Vulnerability
Currently we are not aware of any exploits 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]>.
Currently we are not aware of any exploits 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 / Fix
Linux Kernel Trojan Horse Vulnerability
Solution:
The maintainers of the Linux kernel CVS tree at kernel.bkbits.net have advised that affected users should remove and update exit.c to ensure that they have the proper version of the file.
Solution:
The maintainers of the Linux kernel CVS tree at kernel.bkbits.net have advised that affected users should remove and update exit.c to ensure that they have the proper version of the file.
References
Linux Kernel Trojan Horse Vulnerability
References:
References:
- BK2CVS problem (Larry McVoy ([email protected]) )
- RE: BK2CVS problem (Chad Kitching ([email protected]) )
- Re: BK2CVS problem (Larry McVoy ([email protected]) )