FirefoxWeb browser · Mozilla
CVE-2023-37205
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 · uneditedThe use of RTL Arabic characters in the address bar may have allowed for URL spoofing. This vulnerability affects Firefox < 115.
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 confidenceThis is a URL spoofing vulnerability in Firefox where the use of RTL (Right-to-Left) Arabic characters in the address bar could mislead users about the true destination of a URL. Attackers could exploit RTL override characters to reverse the visual display of domain names, making a malicious URL appear as a trusted site.
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
< 115.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Open Firefox and check the versionIn Firefox, type 'about:firefox' in the address bar and press Enter, or click Help > About Firefox. The version number is displayed at the top of the page.Affected if The displayed version number is less than 115.0 (for example, 114.0, 114.0.1, etc.)
-
Compare against the affected version rangeCompare your installed version to the affected range: any version before 115.0 is affected. Versions 115.0 and later are not affected.Affected if Your installed version is any release prior to 115.0 (for example, 114.x, 113.x, 112.x, etc.)
-
Confirm the vulnerability appliesThis CVE is a URL spoofing flaw involving RTL (right-to-left) override characters in URLs. The vulnerability is present in all affected versions regardless of configuration.Affected if Your Firefox version is below 115.0
You are affected if the installed Firefox version is any release earlier than 115.0.
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.
dbcve · scoped115.0
Upgrade Firefox to version 115 or later. Organizations should deploy the browser update across all managed endpoints and verify the installed version.
Firefox 115.0
- Check current Firefox version by navigating to Help > About Firefox
- If version is below 115.0, trigger automatic update via Help > Check for Updates
- Alternatively, download Firefox 115.0 or later directly from https://www.mozilla.org/firefox/
- Install the downloaded Firefox version, closing the browser if prompted
- Restart Firefox and verify the version is 115.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37205 — 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-2023-37205 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