IBM Java Security Components in IBM SDK, Java Technology Edition 8 before SR2, 7 R1 before SR3 FP20, 7 before SR9 FP20, 6 R1 before SR8 FP15, and 6 before SR16 FP15 allow physically proximate attackers to obtain sensitive information by reading the Kerberos Credential Cache.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Java_2_sdk | Ibm | 5.0.0.0 (including) | 5.0.16.13 (including) |
| Java_sdk | Ibm | 6.0.0.0 (including) | 6.0.16.15 (excluding) |
| Java_sdk | Ibm | 6.1.0.0. (including) | 6.1.8.15 (excluding) |
| Java_sdk | Ibm | 7.0.0.0 (including) | 7.0.9.20 (excluding) |
| Java_sdk | Ibm | 7.1.0.0 (including) | 7.1.3.20 (excluding) |
| Java_sdk | Ibm | 8.0.0.0 (including) | 8.0.2.0 (excluding) |
| Red Hat Enterprise Linux 5 Supplementary | RedHat | java-1.7.0-ibm-1:1.7.0.9.20-1jpp.1.el5 | * |
| Red Hat Enterprise Linux 5 Supplementary | RedHat | java-1.6.0-ibm-1:1.6.0.16.15-1jpp.1.el5 | * |
| Red Hat Enterprise Linux 6 Supplementary | RedHat | java-1.7.1-ibm-1:1.7.1.3.20-1jpp.1.el6_7 | * |
| Red Hat Enterprise Linux 6 Supplementary | RedHat | java-1.6.0-ibm-1:1.6.0.16.15-1jpp.1.el6_7 | * |
| Red Hat Enterprise Linux 7 Supplementary | RedHat | java-1.7.1-ibm-1:1.7.1.3.20-1jpp.1.el7 | * |
| Red Hat Enterprise Linux 7 Supplementary | RedHat | java-1.8.0-ibm-1:1.8.0.2.0-1jpp.1.el7 | * |
| Red Hat Satellite 5.6 | RedHat | java-1.7.0-ibm-1:1.7.0.9.40-1jpp.1.el5 | * |
| Red Hat Satellite 5.6 | RedHat | java-1.7.1-ibm-1:1.7.1.3.40-1jpp.1.el6_7 | * |
| Red Hat Satellite 5.6 | RedHat | spacewalk-java-0:2.0.2-109.el6sat | * |
| Red Hat Satellite 5.7 | RedHat | java-1.7.1-ibm-1:1.7.1.3.40-1jpp.1.el6_7 | * |
| Red Hat Satellite 5.7 | RedHat | spacewalk-java-0:2.3.8-146.el6sat | * |
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.