Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2012-0818

Exposure of Sensitive Information to an Unauthorized Actor

Published: Nov 23, 2012 | Modified: Apr 11, 2025
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
5 MODERATE
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V3
Ubuntu
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2012-0818
CWEhttps://cwe.mitre.org/data/definitions/200.html

RESTEasy before 2.3.1 allows remote attackers to read arbitrary files via an external entity reference in a DOM document, aka an XML external entity (XXE) injection attack.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

NameVendorStart VersionEnd Version
ResteasyRedhat*2.3.0 (including)
ResteasyRedhat1.0.0 (including)1.0.0 (including)
ResteasyRedhat1.0.1 (including)1.0.1 (including)
ResteasyRedhat1.0.2 (including)1.0.2 (including)
ResteasyRedhat1.1 (including)1.1 (including)
ResteasyRedhat1.2 (including)1.2 (including)
ResteasyRedhat2.0.0 (including)2.0.0 (including)
ResteasyRedhat2.0.1 (including)2.0.1 (including)
ResteasyRedhat2.1.0 (including)2.1.0 (including)
ResteasyRedhat2.2.0 (including)2.2.0 (including)
ResteasyRedhat2.2.1 (including)2.2.1 (including)
ResteasyRedhat2.2.2 (including)2.2.2 (including)
ResteasyRedhat2.2.3 (including)2.2.3 (including)
JBEWP 5 for RHEL 5RedHatresteasy-0:1.2.1-10.CP02_patch01.1.ep5.el5*
JBEWP 5 for RHEL 6RedHatresteasy-0:1.2.1-10.CP02_patch01.1.ep5.el6*
JBoss Enterprise BRMS Platform 5.2RedHat*
Red Hat JBoss BPMS 6.0RedHatsecurity*
Red Hat JBoss BRMS 6.0RedHatsecurity*
Red Hat JBoss Enterprise Application Platform 5.1RedHat*
Red Hat JBoss Enterprise Application Platform 5 for RHEL 4RedHatresteasy-0:1.2.1-10.CP02_patch01.1.ep5.el4*
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5RedHatresteasy-0:1.2.1-10.CP02_patch01.1.ep5.el5*
Red Hat JBoss Enterprise Application Platform 5 for RHEL 6RedHatresteasy-0:1.2.1-10.CP02_patch01.1.ep5.el6*
Red Hat JBoss Portal 5.2RedHat*
Red Hat JBoss SOA Platform 5.3RedHat*
Red Hat JBoss Web Platform 5.1RedHat*
Red Hat Storage Console 2.1RedHatorg.ovirt.engine-root-0:2.1.0-16*
Red Hat Storage Console 2.1RedHatotopi-0:1.1.0-1.el6ev*
Red Hat Storage Console 2.1RedHatovirt-host-deploy-0:1.1.0-1.el6ev*
Red Hat Storage Console 2.1RedHatpython-daemon-0:1.5.2-1.el6*
Red Hat Storage Console 2.1RedHatpython-kitchen-0:1.1.1-2.el6ev*
Red Hat Storage Console 2.1RedHatpython-lockfile-0:0.8-5.el6*
Red Hat Storage Console 2.1RedHatpython-ply-0:3.3-7.el6ev*
Red Hat Storage Console 2.1RedHatredhat-access-plugin-storage-0:2.1.0-0.el6rhs*
Red Hat Storage Console 2.1RedHatrhsc-cli-0:2.1.0.0-0.bb3a.el6rhs*
Red Hat Storage Console 2.1RedHatrhsc-log-collector-0:2.1-0.1.el6rhs*
Red Hat Storage Console 2.1RedHatrhsc-sdk-0:2.1.0.0-0.bb3a.el6rhs*
RHEV Manager version 3.0RedHatorg.ovirt.engine-root-0:3.0.3_0001-3*

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

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use