CVE Vulnerabilities

CVE-2011-1416

Exposure of Sensitive Information to an Unauthorized Actor

Published: Mar 11, 2011 | Modified: Mar 24, 2011
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

The Research In Motion (RIM) BlackBerry Torch 9800 with firmware 6.0.0.246 allows attackers to read the contents of memory locations via unknown vectors, as demonstrated by Vincenzo Iozzo, Willem Pinckaers, and Ralf-Philipp Weinmann during a Pwn2Own competition at CanSecWest 2011.

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
Blackberry_torch_9800_firmware Rim 6.0.0.246 (including) 6.0.0.246 (including)
Qt4-x11 Ubuntu karmic *
Qt4-x11 Ubuntu lucid *
Qtwebkit-source Ubuntu devel *
Qtwebkit-source Ubuntu esm-apps/xenial *
Qtwebkit-source Ubuntu maverick *
Qtwebkit-source Ubuntu natty *
Qtwebkit-source Ubuntu oneiric *
Qtwebkit-source Ubuntu precise *
Qtwebkit-source Ubuntu quantal *
Qtwebkit-source Ubuntu raring *
Qtwebkit-source Ubuntu saucy *
Qtwebkit-source Ubuntu trusty *
Qtwebkit-source Ubuntu utopic *
Qtwebkit-source Ubuntu vivid *
Qtwebkit-source Ubuntu wily *
Qtwebkit-source Ubuntu xenial *
Qtwebkit-source Ubuntu yakkety *
Webkit Ubuntu hardy *
Webkit Ubuntu karmic *
Webkit Ubuntu lucid *
Webkit Ubuntu maverick *
Webkit Ubuntu natty *
Webkit Ubuntu oneiric *
Webkit Ubuntu precise *
Webkit Ubuntu quantal *
Webkit Ubuntu raring *
Webkit Ubuntu saucy *
Webkitgtk Ubuntu utopic *
Webkitgtk Ubuntu vivid *

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