CVE Vulnerabilities

CVE-2008-5346

Exposure of Sensitive Information to an Unauthorized Actor

Published: Dec 05, 2008 | Modified: Jul 31, 2019
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
7.1 HIGH
AV:N/AC:M/Au:N/C:C/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

Unspecified vulnerability in Java Runtime Environment (JRE) for Sun JDK and JRE 5.0 Update 16 and earlier; SDK and JRE 1.4.2_18 and earlier; and SDK and JRE 1.3.1_23 or earlier allows untrusted applets and applications to read arbitrary memory via a crafted ZIP file.

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
Jre Sun 1.3.1 1.3.1
Jre Sun 1.3.1_2 1.3.1_2
Jre Sun 1.3.1_03 1.3.1_03
Jre Sun 1.3.1_04 1.3.1_04
Jre Sun 1.3.1_05 1.3.1_05
Jre Sun 1.3.1_06 1.3.1_06
Jre Sun 1.3.1_07 1.3.1_07
Jre Sun 1.3.1_08 1.3.1_08
Jre Sun 1.3.1_09 1.3.1_09
Jre Sun 1.3.1_10 1.3.1_10
Jre Sun 1.3.1_11 1.3.1_11
Jre Sun 1.3.1_12 1.3.1_12
Jre Sun 1.3.1_13 1.3.1_13
Jre Sun 1.3.1_14 1.3.1_14
Jre Sun 1.3.1_15 1.3.1_15
Jre Sun 1.3.1_16 1.3.1_16
Jre Sun 1.3.1_17 1.3.1_17
Jre Sun 1.3.1_18 1.3.1_18
Jre Sun 1.3.1_19 1.3.1_19
Jre Sun 1.3.1_20 1.3.1_20
Jre Sun 1.3.1_21 1.3.1_21
Jre Sun 1.3.1_22 1.3.1_22
Jre Sun 1.3.1_23 1.3.1_23
Jre Sun 1.4.2 1.4.2
Jre Sun 1.4.2_1 1.4.2_1
Jre Sun 1.4.2_2 1.4.2_2
Jre Sun 1.4.2_3 1.4.2_3
Jre Sun 1.4.2_4 1.4.2_4
Jre Sun 1.4.2_5 1.4.2_5
Jre Sun 1.4.2_6 1.4.2_6
Jre Sun 1.4.2_7 1.4.2_7
Jre Sun 1.4.2_8 1.4.2_8
Jre Sun 1.4.2_9 1.4.2_9
Jre Sun 1.4.2_10 1.4.2_10
Jre Sun 1.4.2_11 1.4.2_11
Jre Sun 1.4.2_12 1.4.2_12
Jre Sun 1.4.2_13 1.4.2_13
Jre Sun 1.4.2_14 1.4.2_14
Jre Sun 1.4.2_15 1.4.2_15
Jre Sun 1.4.2_16 1.4.2_16
Jre Sun 1.4.2_17 1.4.2_17
Jre Sun 1.4.2_18 1.4.2_18
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Jre Sun 1.5.0 1.5.0
Extras for RHEL 3 RedHat java-1.4.2-ibm-0:1.4.2.13-1jpp.1.el3 *
Extras for RHEL 4 RedHat java-1.5.0-sun-0:1.5.0.17-1jpp.2.el4 *
Extras for RHEL 4 RedHat java-1.5.0-ibm-1:1.5.0.9-1jpp.4.el4 *
Extras for RHEL 4 RedHat java-1.4.2-ibm-0:1.4.2.13-1jpp.1.el4 *
Red Hat Network Satellite Server v 5.2 RedHat java-1.5.0-ibm-1:1.5.0.9-1jpp.2.el5 *
Supplementary for Red Hat Enterprise Linux 5 RedHat java-1.5.0-sun-0:1.5.0.17-1jpp.2.el5 *
Supplementary for Red Hat Enterprise Linux 5 RedHat java-1.5.0-ibm-1:1.5.0.9-1jpp.2.el5 *
Supplementary for Red Hat Enterprise Linux 5 RedHat java-1.4.2-ibm-0:1.4.2.13-1jpp.1.el5 *

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