Cookie spoofing via insecure document.cookie overwrite
Published Jun 2, 2023 · Updated Jan 10, 2025
Cookie spoofing in Mozilla Firefox, Firefox for Android, and Firefox Focus for Android before 112 allows attackers to alter cookie values. The document.cookie setter in an insecure-origin process accepts a same-name insecure cookie even when the cookie jar retains an existing Secure cookie, leaving script-visible state out of sync. The attack requires a same-site script or network position and can make an application trust an attacker-controlled cookie value that is not sent in HTTP requests.
Summary
What happened
Cookie spoofing in Mozilla Firefox, Firefox for Android, and Firefox Focus for Android before 112 allows attackers to alter cookie values. The document.cookie setter in an insecure-origin process accepts a same-name insecure cookie even when the cookie jar retains an existing Secure cookie, leaving script-visible state out of sync. The attack requires a same-site script or network position and can make an application trust an attacker-controlled cookie value that is not sent in HTTP requests.
The record
- CVE
- CVE-2023-29547
- Published
- Jun 2, 2023
- Updated
- Jan 10, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <112
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- ffdesyncsecure.js proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo