ID CVE-2022-21712
Summary 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.
Vulnerable Configurations
  • cpe:2.3:a:twistedmatrix:twisted:11.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:12.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:12.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:12.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:12.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:13.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:13.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:13.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:14.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:14.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:14.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:15.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:16.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:17.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:17.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:17.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:18.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:18.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:18.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:19.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:19.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:19.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:19.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev0:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev1:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev2:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev3:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev4:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev5:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:20.11.0:dev6:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.2.0:dev0:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.7.0:-:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:twistedmatrix:twisted:21.7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
Base: 5.0 (as of 01-03-2022 - 16:17)
  • Manipulating Web Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
  • Pharming
    A pharming attack occurs when the victim is fooled into entering sensitive data into supposedly trusted locations, such as an online bank site or a trading platform. An attacker can impersonate these supposedly trusted sites and have the victim be directed to his site rather than the originally intended one. Pharming does not require script injection or clicking on malicious links for the attack to succeed.
  • Navigation Remapping To Propagate Malicious Content
    An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, spam-like content, or links to the attackers' code. In general, content-spoofing within an application API can be employed to stage many different types of attacks varied based on the attackers' intent. When the goal is to spread malware, deceptive content is created such as modified links, buttons, or images, that entice users to click on those items, all of which point to a malicious URI. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the destination of various application interface elements.
  • DNS Cache Poisoning
    A domain name server translates a domain name (such as into an IP address that Internet hosts use to contact Internet resources. An adversary modifies a public DNS cache to cause certain names to resolve to incorrect addresses that the adversary specifies. The result is that client applications that rely upon the targeted cache for domain name resolution will be directed not to the actual address of the specified domain name but to some other address. Adversaries can use this to herd clients to sites that install malware on the victim's computer or to masquerade as part of a Pharming attack.
  • Transaction or Event Tampering via Application API Manipulation
    An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.
  • Exploitation of Trusted Credentials
    Attacks on session IDs and resource IDs take advantage of the fact that some software accepts user input without verifying its authenticity. For example, a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or indeed the process that wrote the message to the queue are authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes "trust" other systems because they are behind a firewall. In a similar way servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Session IDs may be guessed due to insufficient randomness, poor protection (passed in the clear), lack of integrity (unsigned), or improperly correlation with access control policy enforcement points. Exposed configuration and properties files that contain system passwords, database connection strings, and such may also give an attacker an edge to identify these identifiers. The net result is that spoofing and impersonation is possible leading to an attacker's ability to break authentication, authorization, and audit controls on the system.
  • Application API Message Manipulation via Man-in-the-Middle
    An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system. Despite the use of MITM software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Man-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Manipulating Writeable Configuration Files
    Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.
  • Application API Navigation Remapping
    An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.
  • Application API Button Hijacking
    An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.
  • SaaS User Request Forgery
    An adversary, through a previously installed malicious application, performs malicious actions against a third-party Software as a Service (SaaS) application (also known as a cloud based application) by leveraging the persistent and implicit trust placed on a trusted user's session. This attack is executed after a trusted user is authenticated into a cloud service, "piggy-backing" on the authenticated session, and exploiting the fact that the cloud service believes it is only interacting with the trusted user. If successful, the actions embedded in the malicious application will be processed and accepted by the targeted SaaS application and executed at the trusted user's privilege level.
  • Cache Poisoning
    An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.
  • Exploit Script-Based APIs
    Some APIs support scripting instructions as arguments. Methods that take scripted instructions (or references to scripted instructions) can be very flexible and powerful. However, if an attacker can specify the script that serves as input to these methods they can gain access to a great deal of functionality. For example, HTML pages support <script> tags that allow scripting languages to be embedded in the page and then interpreted by the receiving web browser. If the content provider is malicious, these scripts can compromise the client application. Some applications may even execute the scripts under their own identity (rather than the identity of the user providing the script) which can allow attackers to perform activities that would otherwise be denied to them.
  • JSON Hijacking (aka JavaScript Hijacking)
    An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. An attacker gets the victim to visit his or her malicious page that contains a script tag whose source points to the vulnerable system with a URL that requests a response from the server containing a JSON object with possibly confidential information. The malicious page also contains malicious code to capture the JSON object returned by the server before any other processing on it can take place, typically by overriding the JavaScript function used to create new objects. This hook allows the malicious code to get access to the creation of each object and transmit the possibly sensitive contents of the captured JSON object to the attackers' server. There is nothing in the browser's security model to prevent the attackers' malicious JavaScript code (originating from attacker's domain) to set up an environment (as described above) to intercept a JSON object response (coming from the vulnerable target system's domain), read its contents and transmit to the attackers' controlled site. The same origin policy protects the domain object model (DOM), but not the JSON.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
cvss-vector via4 AV:N/AC:L/Au:N/C:P/I:N/A:N
Last major update 01-03-2022 - 16:17
Published 07-02-2022 - 22:15
Last modified 01-03-2022 - 16:17
Back to Top