CVE Vulnerabilities

CVE-2019-11712

Cross-Site Request Forgery (CSRF)

Published: Jul 23, 2019 | Modified: Nov 25, 2025
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

POST requests made by NPAPI plugins, such as Flash, that receive a status 308 redirect response can bypass CORS requirements. This can allow an attacker to perform Cross-Site Request Forgery (CSRF) attacks. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

Weakness

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Affected Software

NameVendorStart VersionEnd Version
FirefoxMozilla*60.8.0 (excluding)
FirefoxMozilla*68.0 (excluding)
ThunderbirdMozilla*60.8.0 (excluding)
Red Hat Enterprise Linux 6RedHatfirefox-0:60.8.0-1.el6_10*
Red Hat Enterprise Linux 6RedHatthunderbird-0:60.8.0-1.el6_10*
Red Hat Enterprise Linux 7RedHatfirefox-0:60.8.0-1.el7_6*
Red Hat Enterprise Linux 7RedHatthunderbird-0:60.8.0-1.el7_6*
Red Hat Enterprise Linux 8RedHatfirefox-0:60.8.0-1.el8_0*
Red Hat Enterprise Linux 8RedHatthunderbird-0:60.8.0-1.el8_0*
FirefoxUbuntubionic*
FirefoxUbuntucosmic*
FirefoxUbuntudevel*
FirefoxUbuntudisco*
FirefoxUbuntueoan*
FirefoxUbuntufocal*
FirefoxUbuntugroovy*
FirefoxUbuntuhirsute*
FirefoxUbuntuimpish*
FirefoxUbuntujammy*
FirefoxUbuntukinetic*
FirefoxUbuntulunar*
FirefoxUbuntumantic*
FirefoxUbuntunoble*
FirefoxUbuntutrusty*
FirefoxUbuntuupstream*
FirefoxUbuntuxenial*
Mozjs38Ubuntubionic*
Mozjs38Ubuntuesm-apps/bionic*
Mozjs38Ubuntuupstream*
Mozjs52Ubuntubionic*
Mozjs52Ubuntucosmic*
Mozjs52Ubuntudisco*
Mozjs52Ubuntueoan*
Mozjs52Ubuntuesm-apps/focal*
Mozjs52Ubuntuesm-infra/bionic*
Mozjs52Ubuntufocal*
Mozjs52Ubuntugroovy*
Mozjs52Ubuntuupstream*
Mozjs60Ubuntucosmic*
Mozjs60Ubuntudisco*
Mozjs60Ubuntueoan*
Mozjs60Ubuntuupstream*
ThunderbirdUbuntubionic*
ThunderbirdUbuntucosmic*
ThunderbirdUbuntudevel*
ThunderbirdUbuntudisco*
ThunderbirdUbuntueoan*
ThunderbirdUbuntufocal*
ThunderbirdUbuntugroovy*
ThunderbirdUbuntuhirsute*
ThunderbirdUbuntuimpish*
ThunderbirdUbuntujammy*
ThunderbirdUbuntukinetic*
ThunderbirdUbuntulunar*
ThunderbirdUbuntumantic*
ThunderbirdUbuntunoble*
ThunderbirdUbuntutrusty*
ThunderbirdUbuntuupstream*
ThunderbirdUbuntuxenial*

Potential Mitigations

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
  • For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
  • Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
  • Use the “double-submitted cookie” method as described by Felten and Zeller:
  • When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
  • Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
  • This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]

References