Tornado before 3.2.2 sends arbitrary responses that contain a fixed CSRF token and may be sent with HTTP compression, which makes it easier for remote attackers to conduct a BREACH attack and determine this token via a series of crafted requests.
References
Link | Resource |
---|---|
http://openwall.com/lists/oss-security/2015/05/19/4 | Mailing List Patch Third Party Advisory |
http://www.tornadoweb.org/en/stable/releases/v3.2.2.html | Release Notes Vendor Advisory |
https://bugzilla.novell.com/show_bug.cgi?id=930362 | Issue Tracking Patch Third Party Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=1222816 | Issue Tracking Patch Third Party Advisory |
https://github.com/tornadoweb/tornado/commit/1c36307463b1e8affae100bf9386948e6c1b2308 | Patch |
Configurations
History
No history.
Information
Published : 2020-01-24 18:15
Updated : 2024-02-04 20:39
NVD link : CVE-2014-9720
Mitre link : CVE-2014-9720
CVE.ORG link : CVE-2014-9720
JSON object : View
Products Affected
tornadoweb
- tornado
CWE
CWE-203
Observable Discrepancy