FirefoxWeb browser · Mozilla
CVE-2022-28284
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 · uneditedSVG's <code><use></code> element could have been used to load unexpected content that could have executed script in certain circumstances. While the specification seems to allow this, other browsers do not, and web developers relied on this property for script security so gecko's implementation was aligned with theirs. This vulnerability affects Firefox < 99.
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 confidenceThe Firefox SVG implementation allowed the <use> element to load and execute scripts via external references, contrary to developer security expectations and other browser behaviors. This misalignment created a potential script execution vector that was fixed by aligning Gecko's implementation with other browsers in version 99.
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
< 99.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check Firefox version via browser UIOpen Firefox, click the menu button (three horizontal lines), select Help, then select About Firefox. The version number is displayed in the window that opens.Affected if The displayed version is less than 99.0 (for example, 98.x, 97.x, etc.)
-
Check Firefox version via command lineRun 'firefox --version' or 'firefox -v' in a terminal/command prompt. Some systems may require the full path to the Firefox executable.Affected if The reported version is less than 99.0
-
Check installed package version on LinuxOn systems with package managers, run 'dpkg -l firefox' (Debian/Ubuntu) or 'rpm -qi firefox' (RHEL/Fedora) to query the installed package version.Affected if The package version listed is below 99.0
-
Verify Windows installation versionOpen Control Panel > Programs and Features, locate Mozilla Firefox in the list, and check the Version column.Affected if The installed version is below 99.0
You are affected if Firefox is installed with any version number below 99.0, regardless of operating system.
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 · scoped99.0
Upgrade Firefox to version 99 or later to obtain the corrected SVG <use> element behavior that blocks unexpected script execution.
Firefox 99.0
- Open Firefox and navigate to Menu > Help > About Firefox
- In the About Firefox window, click 'Check for updates' or allow it to automatically check
- If an update is available, click 'Update to the latest version'
- Wait for the download to complete and restart Firefox when prompted
- Alternatively, download Firefox 99.0 or later from the official Mozilla website (www.mozilla.org) and install it
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28284 — 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-2022-28284 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