CVE-2018-12364

NPAPI plugins, such as Adobe Flash, can send non-simple cross-origin requests, bypassing CORS by making a same-origin POST that does a 307 redirect to the target site. This allows for a malicious site to engage in cross-site request forgery (CSRF) attacks. This vulnerability affects Thunderbird < 60, Thunderbird < 52.9, Firefox ESR < 60.1, Firefox ESR < 52.9, and Firefox < 61.

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

Name	Vendor	Start Version	End Version
Enterprise_linux_desktop	Redhat	6.0 (including)	6.0 (including)
Enterprise_linux_desktop	Redhat	7.0 (including)	7.0 (including)
Enterprise_linux_server	Redhat	6.0 (including)	6.0 (including)
Enterprise_linux_server	Redhat	7.0 (including)	7.0 (including)
Enterprise_linux_server_aus	Redhat	7.6 (including)	7.6 (including)
Enterprise_linux_server_eus	Redhat	7.5 (including)	7.5 (including)
Enterprise_linux_server_eus	Redhat	7.6 (including)	7.6 (including)
Enterprise_linux_server_tus	Redhat	7.6 (including)	7.6 (including)
Enterprise_linux_workstation	Redhat	6.0 (including)	6.0 (including)
Enterprise_linux_workstation	Redhat	7.0 (including)	7.0 (including)
Red Hat Enterprise Linux 6	RedHat	firefox-0:60.1.0-5.el6	*
Red Hat Enterprise Linux 6	RedHat	thunderbird-0:52.9.1-1.el6	*
Red Hat Enterprise Linux 7	RedHat	firefox-0:60.1.0-4.el7_5	*
Red Hat Enterprise Linux 7	RedHat	thunderbird-0:52.9.1-1.el7_5	*
Firefox	Ubuntu	artful	*
Firefox	Ubuntu	bionic	*
Firefox	Ubuntu	devel	*
Firefox	Ubuntu	trusty	*
Firefox	Ubuntu	upstream	*
Firefox	Ubuntu	xenial	*
Thunderbird	Ubuntu	artful	*
Thunderbird	Ubuntu	bionic	*
Thunderbird	Ubuntu	devel	*
Thunderbird	Ubuntu	trusty	*
Thunderbird	Ubuntu	upstream	*
Thunderbird	Ubuntu	xenial	*

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]

NVD	https://nvd.nist.gov/vuln/detail/CVE-2018-12364
CWE	https://cwe.mitre.org/data/definitions/352.html

Cross-Site Request Forgery (CSRF)

Weakness

Affected Software

Potential Mitigations

References

CVE-2018-12364

Cross-Site Request Forgery (CSRF)

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References