Skip to content
Fencer Intel
medium 6.8

CVE-2013-6167 json

Mozilla Firefox through 27 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which…

published 12y ago modified 4mo ago also EUVD-2013-5996

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
1
Exploit-DB

Summary

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.

Is CVE-2013-6167 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2013-6167 updated cvss 4.3

Mozilla: browser document.cookie DoS vulnerability

  • Red Hat Enterprise Linux 5 firefox Red Hat Enterprise Linux 6 firefox
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 firefox
    affected: no fix available

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

Timeline

  1. First public exploit (EDB-38798)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-38798 Mozilla Firefox - Cookie Verification Denial of Service dos, 2013-04-04

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

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.