CVE Vulnerabilities

CVE-2011-3744

Exposure of Sensitive Information to an Unauthorized Actor

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

HTML Purifier 4.2.0 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/PHPT/Reporter/SimpleTest.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
Html_purifier Htmlpurifier 4.2.0 (including) 4.2.0 (including)
Php-htmlpurifier Ubuntu artful *
Php-htmlpurifier Ubuntu bionic *
Php-htmlpurifier Ubuntu cosmic *
Php-htmlpurifier Ubuntu devel *
Php-htmlpurifier Ubuntu disco *
Php-htmlpurifier Ubuntu eoan *
Php-htmlpurifier Ubuntu esm-apps/bionic *
Php-htmlpurifier Ubuntu esm-apps/focal *
Php-htmlpurifier Ubuntu esm-apps/jammy *
Php-htmlpurifier Ubuntu esm-apps/noble *
Php-htmlpurifier Ubuntu esm-apps/xenial *
Php-htmlpurifier Ubuntu focal *
Php-htmlpurifier Ubuntu groovy *
Php-htmlpurifier Ubuntu hirsute *
Php-htmlpurifier Ubuntu impish *
Php-htmlpurifier Ubuntu jammy *
Php-htmlpurifier Ubuntu kinetic *
Php-htmlpurifier Ubuntu lucid *
Php-htmlpurifier Ubuntu lunar *
Php-htmlpurifier Ubuntu mantic *
Php-htmlpurifier Ubuntu maverick *
Php-htmlpurifier Ubuntu natty *
Php-htmlpurifier Ubuntu noble *
Php-htmlpurifier Ubuntu oneiric *
Php-htmlpurifier Ubuntu oracular *
Php-htmlpurifier Ubuntu precise *
Php-htmlpurifier Ubuntu quantal *
Php-htmlpurifier Ubuntu raring *
Php-htmlpurifier Ubuntu saucy *
Php-htmlpurifier Ubuntu trusty *
Php-htmlpurifier Ubuntu upstream *
Php-htmlpurifier Ubuntu utopic *
Php-htmlpurifier Ubuntu vivid *
Php-htmlpurifier Ubuntu wily *
Php-htmlpurifier Ubuntu xenial *
Php-htmlpurifier Ubuntu yakkety *
Php-htmlpurifier 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