Skip to content
Fencer Intel
medium 6.5

CVE-2014-9720 json

Tornado XSRF cookie allows side-channel attack against TLS (BREACH attack)

published 2020-01-24 6 y ago modified 2026-06-17 4 mo ago also GHSA-8vpw-mgpf-mpvv , PYSEC-2020-213 , EUVD-2020-0222

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi tornado 3.2.2
  • tornadoweb tornado 3.2.2
  • python-tornado Debian 14, Debian 13, Debian 12 3.2.2-1

debian advisories DEBIAN-CVE-2014-9720

  • python-tornado SLED 12 SP1, SLED 12, SLE Workstation Extension 12 SP1 +1 more 4.2.1-11.1
  • python-backports.ssl_match_hostname SLED 12 SP1, SLED 12, SLE Workstation Extension 12 SP1 +1 more 3.4.0.2-15.1

suse advisories SUSE-SU-2016:1195-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-9720 updated cvss 4.3

python-tornado: XSRF cookie allows side-channel attack against TLS (BREACH)

  • Red Hat Enterprise Linux 7 python-tornado
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi tornado
<3.2.2
3.2.2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.