Skip to content

python-engineio vulnerable to Cross-Site Request Forgery (CSRF)

High severity GitHub Reviewed Published Jul 29, 2019 in miguelgrinberg/python-engineio • Updated Jan 11, 2023

Package

pip python-engineio (pip)

Affected versions

<= 3.8.2

Patched versions

3.9.0

Description

WebSocket cross-origin vulnerability

Impact

This is a Cross-Site Request Forgery (CSRF) vulnerability. It affects Socket.IO and Engine.IO web servers that authenticate clients using cookies.

Patches

python-engineio version 3.9.0 patches this vulnerability by adding server-side Origin header checks.

Workarounds

Do not use cookies for client authentication, or else add a CSRF token to the connection URL.

References

https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)
https://www.christian-schneider.net/CrossSiteWebSocketHijacking.html

For more information

If you have any questions or comments about this advisory:

References

@miguelgrinberg miguelgrinberg published to miguelgrinberg/python-engineio Jul 29, 2019
Published to the GitHub Advisory Database Jul 30, 2019
Reviewed Jun 16, 2020
Last updated Jan 11, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.073%
(32nd percentile)

Weaknesses

CVE ID

CVE-2019-13611

GHSA ID

GHSA-j3jp-gvr5-7hwq

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.