CVE-2013-6167

Publication date 15 February 2014

Last updated 24 July 2024


Ubuntu priority

Mozilla Firefox through 27 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which allows remote attackers to conduct the equivalent of a persistent Logout CSRF attack via a crafted parameter that forces a web application to set a malformed cookie within an HTTP response.

Read the notes from the security team

Status

Package Ubuntu Release Status
firefox 16.10 yakkety Ignored
16.04 LTS xenial Ignored
15.10 wily Ignored end of life
15.04 vivid Ignored end of life
14.10 utopic Ignored end of life
14.04 LTS trusty Not in release
13.10 saucy Ignored end of life
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Ignored
10.04 LTS lucid Ignored end of life
seamonkey 16.10 yakkety Not in release
16.04 LTS xenial Not in release
15.10 wily Not in release
15.04 vivid Not in release
14.10 utopic Not in release
14.04 LTS trusty Not in release
13.10 saucy Not in release
13.04 raring Not in release
12.10 quantal Not in release
12.04 LTS precise Not in release
10.04 LTS lucid Ignored end of life
thunderbird 16.10 yakkety Ignored
16.04 LTS xenial Ignored
15.10 wily Ignored end of life
15.04 vivid Ignored end of life
14.10 utopic Ignored end of life
14.04 LTS trusty Not in release
13.10 saucy Ignored end of life
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Ignored
10.04 LTS lucid Ignored end of life
xulrunner-1.9.2 16.10 yakkety Not in release
16.04 LTS xenial Not in release
15.10 wily Not in release
15.04 vivid Not in release
14.10 utopic Not in release
14.04 LTS trusty Not in release
13.10 saucy Not in release
13.04 raring Not in release
12.10 quantal Not in release
12.04 LTS precise Not in release
10.04 LTS lucid Ignored end of life

Notes


chrisccoulson

The upstream Mozilla bug is marked as wontfix. This only affects cookies set via document.cookie (A similar issue for cookies set via the HTTP Set-Cookie header was fixed in CVE-2016-1939)