CVE Vulnerabilities

CVE-2013-0909

Exposure of Sensitive Information to an Unauthorized Actor

Published: Mar 05, 2013 | Modified: Sep 19, 2017
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

The XSS Auditor in Google Chrome before 25.0.1364.152 allows remote attackers to obtain sensitive HTTP Referer information via unspecified vectors.

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
Chrome Google 25.0.1364.22 25.0.1364.22
Chrome Google 25.0.1364.50 25.0.1364.50
Chrome Google 25.0.1364.88 25.0.1364.88
Chrome Google 25.0.1364.40 25.0.1364.40
Chrome Google 25.0.1364.87 25.0.1364.87
Chrome Google 25.0.1364.86 25.0.1364.86
Chrome Google 25.0.1364.3 25.0.1364.3
Chrome Google 25.0.1364.18 25.0.1364.18
Chrome Google 25.0.1364.70 25.0.1364.70
Chrome Google 25.0.1364.80 25.0.1364.80
Chrome Google 25.0.1364.92 25.0.1364.92
Chrome Google 25.0.1364.31 25.0.1364.31
Chrome Google 25.0.1364.85 25.0.1364.85
Chrome Google 25.0.1364.44 25.0.1364.44
Chrome Google 25.0.1364.0 25.0.1364.0
Chrome Google 25.0.1364.93 25.0.1364.93
Chrome Google 25.0.1364.34 25.0.1364.34
Chrome Google 25.0.1364.28 25.0.1364.28
Chrome Google 25.0.1364.35 25.0.1364.35
Chrome Google 25.0.1364.61 25.0.1364.61
Chrome Google 25.0.1364.89 25.0.1364.89
Chrome Google 25.0.1364.123 25.0.1364.123
Chrome Google 25.0.1364.121 25.0.1364.121
Chrome Google 25.0.1364.21 25.0.1364.21
Chrome Google 25.0.1364.48 25.0.1364.48
Chrome Google 25.0.1364.118 25.0.1364.118
Chrome Google 25.0.1364.36 25.0.1364.36
Chrome Google 25.0.1364.42 25.0.1364.42
Chrome Google 25.0.1364.9 25.0.1364.9
Chrome Google 25.0.1364.74 25.0.1364.74
Chrome Google 25.0.1364.39 25.0.1364.39
Chrome Google 25.0.1364.16 25.0.1364.16
Chrome Google 25.0.1364.114 25.0.1364.114
Chrome Google 25.0.1364.54 25.0.1364.54
Chrome Google 25.0.1364.62 25.0.1364.62
Chrome Google 25.0.1364.67 25.0.1364.67
Chrome Google 25.0.1364.98 25.0.1364.98
Chrome Google 25.0.1364.115 25.0.1364.115
Chrome Google * 25.0.1364.126
Chrome Google 25.0.1364.41 25.0.1364.41
Chrome Google 25.0.1364.124 25.0.1364.124
Chrome Google 25.0.1364.45 25.0.1364.45
Chrome Google 25.0.1364.19 25.0.1364.19
Chrome Google 25.0.1364.13 25.0.1364.13
Chrome Google 25.0.1364.66 25.0.1364.66
Chrome Google 25.0.1364.1 25.0.1364.1
Chrome Google 25.0.1364.15 25.0.1364.15
Chrome Google 25.0.1364.56 25.0.1364.56
Chrome Google 25.0.1364.30 25.0.1364.30
Chrome Google 25.0.1364.52 25.0.1364.52
Chrome Google 25.0.1364.77 25.0.1364.77
Chrome Google 25.0.1364.110 25.0.1364.110
Chrome Google 25.0.1364.73 25.0.1364.73
Chrome Google 25.0.1364.14 25.0.1364.14
Chrome Google 25.0.1364.25 25.0.1364.25
Chrome Google 25.0.1364.113 25.0.1364.113
Chrome Google 25.0.1364.43 25.0.1364.43
Chrome Google 25.0.1364.57 25.0.1364.57
Chrome Google 25.0.1364.5 25.0.1364.5
Chrome Google 25.0.1364.12 25.0.1364.12
Chrome Google 25.0.1364.76 25.0.1364.76
Chrome Google 25.0.1364.116 25.0.1364.116
Chrome Google 25.0.1364.112 25.0.1364.112
Chrome Google 25.0.1364.24 25.0.1364.24
Chrome Google 25.0.1364.10 25.0.1364.10
Chrome Google 25.0.1364.55 25.0.1364.55
Chrome Google 25.0.1364.95 25.0.1364.95
Chrome Google 25.0.1364.47 25.0.1364.47
Chrome Google 25.0.1364.51 25.0.1364.51
Chrome Google 25.0.1364.11 25.0.1364.11
Chrome Google 25.0.1364.120 25.0.1364.120
Chrome Google 25.0.1364.27 25.0.1364.27
Chrome Google 25.0.1364.68 25.0.1364.68
Chrome Google 25.0.1364.8 25.0.1364.8
Chrome Google 25.0.1364.99 25.0.1364.99
Chrome Google 25.0.1364.58 25.0.1364.58
Chrome Google 25.0.1364.79 25.0.1364.79
Chrome Google 25.0.1364.84 25.0.1364.84
Chrome Google 25.0.1364.37 25.0.1364.37
Chrome Google 25.0.1364.119 25.0.1364.119
Chrome Google 25.0.1364.38 25.0.1364.38
Chrome Google 25.0.1364.72 25.0.1364.72
Chrome Google 25.0.1364.63 25.0.1364.63
Chrome Google 25.0.1364.78 25.0.1364.78
Chrome Google 25.0.1364.82 25.0.1364.82
Chrome Google 25.0.1364.117 25.0.1364.117
Chrome Google 25.0.1364.33 25.0.1364.33
Chrome Google 25.0.1364.91 25.0.1364.91
Chrome Google 25.0.1364.46 25.0.1364.46
Chrome Google 25.0.1364.32 25.0.1364.32
Chrome Google 25.0.1364.122 25.0.1364.122
Chrome Google 25.0.1364.29 25.0.1364.29
Chrome Google 25.0.1364.49 25.0.1364.49
Chrome Google 25.0.1364.53 25.0.1364.53
Chrome Google 25.0.1364.65 25.0.1364.65
Chrome Google 25.0.1364.75 25.0.1364.75
Chrome Google 25.0.1364.90 25.0.1364.90
Chrome Google 25.0.1364.2 25.0.1364.2
Chrome Google 25.0.1364.23 25.0.1364.23
Chrome Google 25.0.1364.125 25.0.1364.125
Chrome Google 25.0.1364.81 25.0.1364.81
Chrome Google 25.0.1364.17 25.0.1364.17
Chrome Google 25.0.1364.26 25.0.1364.26
Chrome Google 25.0.1364.108 25.0.1364.108
Chrome Google 25.0.1364.20 25.0.1364.20
Chrome Google 25.0.1364.7 25.0.1364.7

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