CVE-2014-9720

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.

Published: 2020-01-24 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2014-9720 is rated Moderate Risk (51.7/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.78%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2014-9720

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 0.90% 0.78% -0.12%
2 2025-03-30 2.36% 0.90% -1.46%
3 2025-03-29 — 2.36% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2014-9720

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2014-9720

GitHub Security Advisory for CVE-2014-9720

GHSA-8vpw-mgpf-mpvv · Severity: high · Ecosystem: pip — Tornado XSRF cookie allows side-channel attack against TLS (BREACH attack)

OS Trackers for CVE-2014-9720

vendor priority summary link
debian not yet assigned CVE-2014-9720 not yet assigned priority: Debian including 1 source packages (python-tornado), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2014-9720
redhat medium — https://access.redhat.com/security/cve/CVE-2014-9720
ubuntu low CVE-2014-9720 low priority: Ubuntu including 1 source packages (python-tornado), 13 status rows across 13 suites (artful, bionic, cosmic, disco, precise, trusty, upstream, utopic, vivid, wily, xenial, yakkety, zesty): ignored 7, not-affected 4, DNE 1, released 1. https://ubuntu.com/security/CVE-2014-9720

Affected software / configurations for CVE-2014-9720

Vendor Product Version Raw CPE
tornadoweb tornado < 3.2.2 cpe:2.3:a:tornadoweb:tornado:*:*:*:*:*:*:*:*

References for CVE-2014-9720

cvelogic Threat Intelligence