CVE Vulnerabilities

CVE-2009-2031

Exposure of Sensitive Information to an Unauthorized Actor

Published: Jun 11, 2009 | Modified: Jun 19, 2009
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

smbfs in Sun OpenSolaris snv_84 through snv_110, when default mount permissions are used, allows local users to read arbitrary files, and list arbitrary directories, on CIFS volumes.

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
Opensolaris Sun snv_101 snv_101
Opensolaris Sun snv_90 snv_90
Opensolaris Sun snv_93 snv_93
Opensolaris Sun snv_110 snv_110
Opensolaris Sun snv_85 snv_85
Opensolaris Sun snv_87 snv_87
Opensolaris Sun snv_87 snv_87
Opensolaris Sun snv_91 snv_91
Opensolaris Sun snv_92 snv_92
Opensolaris Sun snv_85 snv_85
Opensolaris Sun snv_104 snv_104
Opensolaris Sun snv_103 snv_103
Opensolaris Sun snv_105 snv_105
Opensolaris Sun snv_88 snv_88
Opensolaris Sun snv_93 snv_93
Opensolaris Sun snv_103 snv_103
Opensolaris Sun snv_84 snv_84
Opensolaris Sun snv_106 snv_106
Opensolaris Sun snv_106 snv_106
Opensolaris Sun snv_86 snv_86
Opensolaris Sun snv_100 snv_100
Opensolaris Sun snv_107 snv_107
Opensolaris Sun snv_89 snv_89
Opensolaris Sun snv_90 snv_90
Opensolaris Sun snv_96 snv_96
Opensolaris Sun snv_99 snv_99
Opensolaris Sun snv_107 snv_107
Opensolaris Sun snv_97 snv_97
Opensolaris Sun snv_100 snv_100
Opensolaris Sun snv_96 snv_96
Opensolaris Sun snv_94 snv_94
Opensolaris Sun snv_86 snv_86
Opensolaris Sun snv_98 snv_98
Opensolaris Sun snv_98 snv_98
Opensolaris Sun snv_109 snv_109
Opensolaris Sun snv_95 snv_95
Opensolaris Sun snv_108 snv_108
Opensolaris Sun snv_102 snv_102
Opensolaris Sun snv_105 snv_105
Opensolaris Sun snv_108 snv_108
Opensolaris Sun snv_95 snv_95
Opensolaris Sun snv_88 snv_88
Opensolaris Sun snv_84 snv_84
Opensolaris Sun snv_92 snv_92
Opensolaris Sun snv_104 snv_104
Opensolaris Sun snv_94 snv_94
Opensolaris Sun snv_101 snv_101
Opensolaris Sun snv_97 snv_97
Opensolaris Sun snv_99 snv_99
Opensolaris Sun snv_109 snv_109
Opensolaris Sun snv_102 snv_102
Opensolaris Sun snv_110 snv_110
Opensolaris Sun snv_91 snv_91
Opensolaris Sun snv_89 snv_89

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