CVE Vulnerabilities

CVE-2011-3699

Exposure of Sensitive Information to an Unauthorized Actor

Published: Sep 23, 2011 | Modified: Mar 13, 2012
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
LOW

John Lim ADOdb Library for PHP 5.11 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by tests/test-active-record.php and certain other files.

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
Adodb John_lim 5.11 (including) 5.11 (including)
Libphp-adodb Ubuntu artful *
Libphp-adodb Ubuntu bionic *
Libphp-adodb Ubuntu cosmic *
Libphp-adodb Ubuntu devel *
Libphp-adodb Ubuntu disco *
Libphp-adodb Ubuntu eoan *
Libphp-adodb Ubuntu esm-apps/bionic *
Libphp-adodb Ubuntu esm-apps/focal *
Libphp-adodb Ubuntu esm-apps/jammy *
Libphp-adodb Ubuntu esm-apps/noble *
Libphp-adodb Ubuntu esm-apps/xenial *
Libphp-adodb Ubuntu focal *
Libphp-adodb Ubuntu groovy *
Libphp-adodb Ubuntu hardy *
Libphp-adodb Ubuntu hirsute *
Libphp-adodb Ubuntu impish *
Libphp-adodb Ubuntu jammy *
Libphp-adodb Ubuntu kinetic *
Libphp-adodb Ubuntu lucid *
Libphp-adodb Ubuntu lunar *
Libphp-adodb Ubuntu mantic *
Libphp-adodb Ubuntu maverick *
Libphp-adodb Ubuntu natty *
Libphp-adodb Ubuntu noble *
Libphp-adodb Ubuntu oneiric *
Libphp-adodb Ubuntu precise *
Libphp-adodb Ubuntu quantal *
Libphp-adodb Ubuntu raring *
Libphp-adodb Ubuntu saucy *
Libphp-adodb Ubuntu trusty *
Libphp-adodb Ubuntu upstream *
Libphp-adodb Ubuntu utopic *
Libphp-adodb Ubuntu vivid *
Libphp-adodb Ubuntu wily *
Libphp-adodb Ubuntu xenial *
Libphp-adodb Ubuntu yakkety *
Libphp-adodb Ubuntu zesty *

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