CVE Vulnerabilities

CVE-2022-21712

Exposure of Sensitive Information to an Unauthorized Actor

Published: Feb 07, 2022 | Modified: Nov 25, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM

twisted is an event-driven networking engine written in Python. In affected versions twisted exposes cookies and authorization headers when following cross-origin redirects. This issue is present in the twited.web.RedirectAgent and twisted.web. BrowserLikeRedirectAgent functions. Users are advised to upgrade. There are no known workarounds.

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
Twisted Twisted 11.1.0 (including) 22.1.0 (excluding)
Red Hat OpenStack Platform 16.1 RedHat python-twisted-0:16.4.1-19.el8ost *
Red Hat OpenStack Platform 16.2 RedHat python-twisted-0:16.4.1-19.el8ost *
Twisted Ubuntu bionic *
Twisted Ubuntu devel *
Twisted Ubuntu esm-infra-legacy/trusty *
Twisted Ubuntu esm-infra/xenial *
Twisted Ubuntu focal *
Twisted Ubuntu impish *
Twisted Ubuntu jammy *
Twisted Ubuntu kinetic *
Twisted Ubuntu lunar *
Twisted Ubuntu mantic *
Twisted Ubuntu noble *
Twisted Ubuntu oracular *
Twisted Ubuntu trusty *
Twisted Ubuntu trusty/esm *
Twisted Ubuntu upstream *
Twisted Ubuntu xenial *

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