dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
FirefoxWeb browser · Mozilla

CVE-2013-1675

MEDIUM · 6.5 CVSS v3.1 Published 2013-05-16
Fix available
A fix is available. Upgrade to 17.0.6 / 21.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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
Mozilla Firefox before 21.0, Firefox ESR 17.x before 17.0.6, Thunderbird before 17.0.6, and Thunderbird ESR 17.x before 17.0.6 do not properly initialize data structures for the nsDOMSVGZoomEvent::mPreviousScale and nsDOMSVGZoomEvent::mNewScale functions, which allows remote attackers to obtain sensitive information from process memory via a crafted web site.

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

Mozilla Firefox and Thunderbird fail to initialize the mPreviousScale and mNewScale data structures in the nsDOMSVGZoomEvent functions before use. This causes uninitialized stack/heap memory contents to be accessible when a crafted webpage triggers SVG zoom events, allowing remote attackers to read sensitive process memory.

MitigationUpgrade Firefox to version 21.0 or later (or ESR 17.0.6+), and Thunderbird to version 17.0.6 or later. Alternatively, disable SVG support in the browser if upgrading is not immediately feasible.

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:< 21.0>= 17.0, < 17.0.6
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.04
Debian LinuxOperating system
Affected:= 7.0
Gluster Storage Server For On PremiseApplication
Affected:= 2.1
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 5.9= 6.4
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 5.0_s390x= 6.0_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 5.9_s390x= 6.4_s390x

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
High
Integrity
None
Availability
None

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

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

  1. Identify installed Firefox version
    In Firefox, go to Help > About Firefox, or type 'about:support' in the address bar, or run 'firefox --version' from command line
    Affected if Version is < 21.0 OR (>= 17.0 AND < 17.0.6)
  2. Confirm SVG support is enabled
    In Firefox, type 'about:config' and search for 'svg', ensure 'svg.enabled' is not set to false (default is true)
    Affected if SVG support is disabled - user is not affected; if enabled - proceed to next check
  3. Check browser usage on shared systems
    For multi-user systems, check browser history or cache directories in user profiles for any recently visited pages containing SVG content
    Affected if Users have browsed untrusted websites - potential exposure vector exists

A user is affected if they are running Firefox version < 21.0 or between 17.0 and 17.0.6, with SVG support enabled, and have visited or could visit a crafted webpage triggering the SVG zoom event handler.

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 17.0.6 / 21.0 or later
Fixed in 17.0.621.0
Interim mitigation

Upgrade Firefox to version 21.0 or later (or ESR 17.0.6+), and Thunderbird to version 17.0.6 or later. Alternatively, disable SVG support in the browser if upgrading is not immediately feasible.

Recommended fix High confidence

Firefox 21.0 or later; Firefox ESR 17.0.6 or later; Thunderbird 17.0.6 or later

  1. Check the currently installed Firefox version by navigating to 'Help' > 'About Firefox'
  2. For Ubuntu/Debian systems, run: sudo apt-get update && sudo apt-get upgrade firefox
  3. For Enterprise Linux systems, run: sudo yum update firefox
  4. For Red Hat systems, run: sudo rhn_patch --update firefox
  5. Alternatively, download the latest Firefox from the official Mozilla website (https://www.mozilla.org/firefox/)
  6. Restart Firefox after the upgrade completes
  7. Verify the installed version is 21.0 or later (or ESR 17.0.6 or later)
Caveat Users on very old systems may experience compatibility issues with newer Firefox versions if they rely on legacy add-ons or older plugins

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

Fix this in Firefox Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1675 — 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-2013-1675 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