First published: Thu Nov 04 2010(Updated: )
Description of problem: Structure sockaddr_tipc is copied to userland with padding bytes after "id" field in union field "name" unitialized. It leads to leaking of contents of kernel stack memory. We have to initialize them to zero. Reference: <a href="http://marc.info/?l=linux-netdev&m=128854507420917&w=2">http://marc.info/?l=linux-netdev&m=128854507420917&w=2</a> <a href="http://seclists.org/oss-sec/2010/q4/94">http://seclists.org/oss-sec/2010/q4/94</a> Acknowledgements: Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux-2.6 | ||
Linux Kernel | <2.6.37 | |
Linux Kernel | =2.6.37 | |
Linux Kernel | =2.6.37-rc1 | |
Debian Linux | =5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3877 has been classified as a high-severity vulnerability due to its potential to leak sensitive kernel stack memory data.
CVE-2010-3877 poses a security risk by allowing unauthorized access to potentially sensitive data stored in the kernel stack via uninitialized padding bytes.
To mitigate CVE-2010-3877, ensure that the struct sockaddr_tipc is properly initialized to set padding bytes to zero.
CVE-2010-3877 affects versions of the Linux kernel prior to 2.6.37 as well as Debian Linux version 5.0.
Yes, a patch is available that addresses CVE-2010-3877 by ensuring proper initialization of the sockaddr_tipc structure.