CVE Vulnerabilities

CVE-2011-4915

Exposure of Sensitive Information to an Unauthorized Actor

Published: Feb 20, 2020 | Modified: Feb 25, 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
RedHat/V3
Ubuntu
LOW

fs/proc/base.c in the Linux kernel through 3.1 allows local users to obtain sensitive keystroke information via access to /proc/interrupts.

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 * 3.1 (including)
Linux Ubuntu devel *
Linux Ubuntu esm-infra-legacy/trusty *
Linux Ubuntu hardy *
Linux Ubuntu lucid *
Linux Ubuntu maverick *
Linux Ubuntu natty *
Linux Ubuntu oneiric *
Linux Ubuntu precise *
Linux Ubuntu quantal *
Linux Ubuntu raring *
Linux Ubuntu saucy *
Linux Ubuntu trusty *
Linux Ubuntu trusty/esm *
Linux Ubuntu upstream *
Linux-armadaxp Ubuntu precise *
Linux-armadaxp Ubuntu quantal *
Linux-armadaxp Ubuntu upstream *
Linux-ec2 Ubuntu lucid *
Linux-ec2 Ubuntu maverick *
Linux-ec2 Ubuntu upstream *
Linux-flo Ubuntu devel *
Linux-flo Ubuntu trusty *
Linux-flo Ubuntu upstream *
Linux-fsl-imx51 Ubuntu lucid *
Linux-fsl-imx51 Ubuntu upstream *
Linux-goldfish Ubuntu devel *
Linux-goldfish Ubuntu saucy *
Linux-goldfish Ubuntu trusty *
Linux-goldfish Ubuntu upstream *
Linux-grouper Ubuntu devel *
Linux-grouper Ubuntu saucy *
Linux-grouper Ubuntu trusty *
Linux-grouper Ubuntu upstream *
Linux-lts-backport-maverick Ubuntu lucid *
Linux-lts-backport-maverick Ubuntu upstream *
Linux-lts-backport-natty Ubuntu lucid *
Linux-lts-backport-natty Ubuntu upstream *
Linux-lts-backport-oneiric Ubuntu lucid *
Linux-lts-backport-oneiric Ubuntu upstream *
Linux-lts-quantal Ubuntu precise *
Linux-lts-raring Ubuntu precise *
Linux-lts-raring Ubuntu upstream *
Linux-lts-saucy Ubuntu precise *
Linux-lts-saucy Ubuntu upstream *
Linux-maguro Ubuntu devel *
Linux-maguro Ubuntu saucy *
Linux-maguro Ubuntu trusty *
Linux-maguro Ubuntu upstream *
Linux-mako Ubuntu devel *
Linux-mako Ubuntu saucy *
Linux-mako Ubuntu trusty *
Linux-mako Ubuntu upstream *
Linux-manta Ubuntu devel *
Linux-manta Ubuntu saucy *
Linux-manta Ubuntu trusty *
Linux-manta Ubuntu upstream *
Linux-mvl-dove Ubuntu lucid *
Linux-mvl-dove Ubuntu maverick *
Linux-mvl-dove Ubuntu upstream *
Linux-ti-omap4 Ubuntu maverick *
Linux-ti-omap4 Ubuntu natty *
Linux-ti-omap4 Ubuntu oneiric *
Linux-ti-omap4 Ubuntu precise *
Linux-ti-omap4 Ubuntu quantal *
Linux-ti-omap4 Ubuntu raring *
Linux-ti-omap4 Ubuntu saucy *
Linux-ti-omap4 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