CVE Vulnerabilities


Exposure of Sensitive Information to an Unauthorized Actor

Published: Feb 05, 2013 | Modified: Feb 07, 2013
CVSS 3.x
CVSS 2.x
7.1 HIGH

The PowerVR SGX driver in Android before 2.3.6 allows attackers to obtain potentially sensitive information from kernel stack memory via an application that uses a crafted length parameter in a request to the pvrsrvkm device.


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
Android Google 1.0 1.0
Android Google 1.1 1.1
Android Google 1.5 1.5
Android Google 1.6 1.6
Android Google 2.0 2.0
Android Google 2.0.1 2.0.1
Android Google 2.1 2.1
Android Google 2.2 2.2
Android Google 2.2.1 2.2.1
Android Google 2.2.2 2.2.2
Android Google 2.2.3 2.2.3
Android Google 2.3 2.3
Android Google 2.3.1 2.3.1
Android Google 2.3.2 2.3.2
Android Google 2.3.3 2.3.3
Android Google 2.3.4 2.3.4
Android Google * 2.3.5
Linux-flo Ubuntu esm-apps/xenial *
Linux-flo Ubuntu trusty *
Linux-flo Ubuntu utopic *
Linux-flo Ubuntu vivid *
Linux-flo Ubuntu vivid/stable-phone-overlay *
Linux-flo Ubuntu wily *
Linux-flo Ubuntu xenial *
Linux-flo Ubuntu yakkety *
Linux-goldfish Ubuntu esm-apps/xenial *
Linux-goldfish Ubuntu saucy *
Linux-goldfish Ubuntu trusty *
Linux-goldfish Ubuntu utopic *
Linux-goldfish Ubuntu vivid *
Linux-goldfish Ubuntu wily *
Linux-goldfish Ubuntu xenial *
Linux-goldfish Ubuntu yakkety *
Linux-goldfish Ubuntu zesty *
Linux-grouper Ubuntu saucy *
Linux-grouper Ubuntu trusty *
Linux-grouper Ubuntu utopic *
Linux-maguro Ubuntu saucy *
Linux-maguro Ubuntu trusty *
Linux-mako Ubuntu esm-apps/xenial *
Linux-mako Ubuntu saucy *
Linux-mako Ubuntu trusty *
Linux-mako Ubuntu utopic *
Linux-mako Ubuntu vivid *
Linux-mako Ubuntu vivid/stable-phone-overlay *
Linux-mako Ubuntu wily *
Linux-mako Ubuntu xenial *
Linux-mako Ubuntu yakkety *
Linux-manta Ubuntu saucy *
Linux-manta Ubuntu trusty *
Linux-manta Ubuntu utopic *
Linux-manta Ubuntu vivid *
Linux-manta Ubuntu wily *

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.