CVE Vulnerabilities

CVE-2003-1481

Exposure of Sensitive Information to an Unauthorized Actor

Published: Dec 31, 2003 | Modified: Jul 29, 2017
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

CommuniGate Pro 3.1 through 4.0.6 sends the session ID in the referer field for an HTTP request for an image, which allows remote attackers to hijack mail sessions via an e-mail with an IMG tag that references a malicious URL that captures the referer.

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
Communigate_pro Stalker 3.1 3.1
Communigate_pro Stalker 3.2.4 3.2.4
Communigate_pro Stalker 3.2_b5 3.2_b5
Communigate_pro Stalker 3.2_b7 3.2_b7
Communigate_pro Stalker 3.3.2 3.3.2
Communigate_pro Stalker 3.3_b1 3.3_b1
Communigate_pro Stalker 3.3_b2 3.3_b2
Communigate_pro Stalker 3.4_b3 3.4_b3
Communigate_pro Stalker 4.0.1 4.0.1
Communigate_pro Stalker 4.0.2 4.0.2
Communigate_pro Stalker 4.0.3 4.0.3
Communigate_pro Stalker 4.0.6 4.0.6
Communigate_pro Stalker 4.0_b2 4.0_b2
Communigate_pro Stalker 4.0_b3 4.0_b3

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