dbcve.org
FirefoxWeb browser · Mozilla

CVE-2023-29547

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-02
Fix available
A fix is available. Upgrade to 102.10 / 112.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, when it should have silently failed. This could have led to a desynchronization in expected results when reading from the secure cookie. This vulnerability affects Firefox for Android < 112, Firefox < 112, and Focus for Android < 112.

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 confidence

Firefox's cookie jar incorrectly allowed an insecure (non-HTTPS) cookie to be set for a domain that already had a secure cookie, when this operation should have silently failed. This breaks the expected cookie isolation model and can cause desynchronization when the application reads cookies, potentially leading to unexpected behavior or security bypasses in web applications relying on secure cookie semantics.

MitigationUpgrade Firefox, Firefox for Android, and Focus for Android to version 112 or later to obtain the patched browser. For enterprise deployments, push the browser update via standard software distribution mechanisms.

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
FirefoxWeb browser
Affected:< 112.0
Firefox EsrWeb browser
Affected:< 102.10
FocusApplication
Affected:< 112.0

CVSS 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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Firefox desktop version
    Navigate to Firefox menu > Help > About Firefox, or enter 'about:support' in the address bar and look at the 'Version' field
    Affected if Version is lower than 112.0 (for example, 111.0, 110.0, etc.)
  2. Check Firefox ESR version
    Navigate to Firefox ESR menu > Help > About Firefox ESR, or enter 'about:support' in the address bar and look at the 'Version' field
    Affected if Version is lower than 102.10 (for example, 102.9, 102.8, etc.)
  3. Check Mozilla Focus version
    Open Focus app, tap the menu icon > Settings > About Mozilla Focus, or check the version in your device's app settings
    Affected if Version is lower than 112.0 (for example, 111.x, 110.x, etc.)

You are affected if any installed Firefox desktop, Firefox ESR, or Focus browser version falls below the respective threshold (112.0 for Firefox/Focus, 102.10 for ESR).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 102.10 / 112.0 or later
Fixed in 102.10112.0
Interim mitigation

Upgrade Firefox, Firefox for Android, and Focus for Android to version 112 or later to obtain the patched browser. For enterprise deployments, push the browser update via standard software distribution mechanisms.

Recommended fix High confidence

Firefox 112.0, Firefox ESR 102.10, Focus for Android 112.0

  1. Check current Firefox version via Help > About Firefox (or Firefox ESR)
  2. Download Firefox 112.0 or later from the official Mozilla website (www.mozilla.org)
  3. Download Firefox ESR 102.10 or later from the official Mozilla website for ESR installations
  4. For Android devices, update Focus to version 112.0 or later via Google Play Store
  5. Restart the browser after installation to apply the update
  6. Verify the version has been updated to the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29547 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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