CVE-2010-3877: Low severity linux kernel vulnerability
Description of problem: Structure sockaddrtipc 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: http://marc.info/?l=linux-netdev&m=128854507420917&w=2 http://seclists.org/oss-sec/2010/q4/94
Acknowledgements:
Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue.
Other sources
The getname function in net/tipc/socket.c in the Linux kernel before 2.6.37-rc2 does not initialize a certain structure, which allows local users to obtain potentially sensitive information from kernel stack memory by reading a copy of this structure.
— Launchpad
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3877?
CVE-2010-3877 has been classified as a high-severity vulnerability due to its potential to leak sensitive kernel stack memory data.
How does CVE-2010-3877 affect system security?
CVE-2010-3877 poses a security risk by allowing unauthorized access to potentially sensitive data stored in the kernel stack via uninitialized padding bytes.
How do I fix CVE-2010-3877?
To mitigate CVE-2010-3877, ensure that the struct sockaddr_tipc is properly initialized to set padding bytes to zero.
Which systems are affected by CVE-2010-3877?
CVE-2010-3877 affects versions of the Linux kernel prior to 2.6.37 as well as Debian Linux version 5.0.
Is there a patch available for CVE-2010-3877?
Yes, a patch is available that addresses CVE-2010-3877 by ensuring proper initialization of the sockaddr_tipc structure.