CVE Vulnerabilities

CVE-2010-3078

Exposure of Sensitive Information to an Unauthorized Actor

Published: Sep 21, 2010 | Modified: Aug 11, 2020
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
2.1 MODERATE
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V3
Ubuntu

The xfs_ioc_fsgetxattr function in fs/xfs/linux-2.6/xfs_ioctl.c in the Linux kernel before 2.6.36-rc4 does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via an ioctl call.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Linux_kernel Linux * 2.6.35.4
Linux_kernel Linux 2.6.36 2.6.36
Linux_kernel Linux 2.6.36 2.6.36
Linux_kernel Linux 2.6.36 2.6.36
Linux_kernel Linux 2.6.36 2.6.36
Red Hat Enterprise Linux 5 RedHat kernel-0:2.6.18-194.26.1.el5 *
Red Hat Enterprise Linux 6 RedHat kernel-0:2.6.32-71.14.1.el6 *
Linux Ubuntu hardy *
Linux Ubuntu jaunty *
Linux Ubuntu karmic *
Linux Ubuntu lucid *
Linux Ubuntu upstream *
Linux-ec2 Ubuntu karmic *
Linux-ec2 Ubuntu lucid *
Linux-ec2 Ubuntu maverick *
Linux-ec2 Ubuntu upstream *
Linux-fsl-imx51 Ubuntu karmic *
Linux-fsl-imx51 Ubuntu lucid *
Linux-fsl-imx51 Ubuntu upstream *
Linux-lts-backport-maverick Ubuntu lucid *
Linux-lts-backport-maverick Ubuntu upstream *
Linux-mvl-dove Ubuntu karmic *
Linux-mvl-dove Ubuntu lucid *
Linux-mvl-dove Ubuntu maverick *
Linux-mvl-dove Ubuntu upstream *
Linux-source-2.6.15 Ubuntu upstream *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References