CVE-2004-0871
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMozilla does not prevent cookies that are sent over an insecure channel (HTTP) from also being sent over a secure channel (HTTPS/SSL) in the same domain, which could allow remote attackers to steal cookies and conduct unauthorized activities, aka "Cross Security Boundary Cookie Injection."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMozilla browser allows cookies set over insecure HTTP to also be sent over secure HTTPS channels within the same domain. This enables attackers on insecure networks to intercept cookies via HTTP and then use them to hijack authenticated HTTPS sessions, crossing the security boundary between insecure and secure channels.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Mozilla browser versionOpen the Mozilla browser and navigate to Help > About Mozilla, or check the application file properties of the Mozilla executable. Alternatively, run 'mozilla -version' from command line if available.Affected if The installed version is exactly 0.9.2
-
Verify HTTP cookie leakage to HTTPSVisit a site over HTTP, then inspect cookies for that domain. Visit an HTTPS version of the same domain and check if those same cookies (without the 'secure' flag) are being sent in the HTTPS request.Affected if Cookies set over HTTP are being transmitted to HTTPS endpoints within the same domain, indicating the secure boundary is not enforced
-
Check cookie attributesUsing browser developer tools or a cookie inspector extension, examine cookies set by HTTP connections. Look for the 'secure' flag status on cookies from domains accessed via both HTTP and HTTPS.Affected if Cookies created during HTTP sessions lack the 'secure' attribute and are still sent when accessing HTTPS versions of the same domain
If running Mozilla version 0.9.2 and cookies set over insecure HTTP are being sent to secure HTTPS connections within the same domain, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate or replace the affected Mozilla browser installation to a version that properly isolates HTTP cookies from HTTPS connections, or migrate to a modern browser that enforces secure cookie attributes.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2004-0871 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data