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.
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.
Link | Tags |
---|---|
http://www.tornadoweb.org/en/stable/releases/v3.2.2.html | release notes vendor advisory |
https://github.com/tornadoweb/tornado/commit/1c36307463b1e8affae100bf9386948e6c1b2308 | patch |
https://bugzilla.novell.com/show_bug.cgi?id=930362 | issue tracking third party advisory patch |
https://bugzilla.redhat.com/show_bug.cgi?id=1222816 | issue tracking third party advisory patch |
http://openwall.com/lists/oss-security/2015/05/19/4 | mailing list third party advisory patch |