basicsecurity.net
Proof, not just disclosure.
Threats / Mozilla / CVE-2013-1690
CVE-2013-1690 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Mozilla Firefox and Thunderbird vulnerability

Mozilla Firefox and Thunderbird improperly handle onreadystatechange events during page reloads, allowing remote attackers to trigger denial-of-service or code execution via malicious websites.

Verdict

Today item — known-exploited.

Remote attackers can exploit improper event handling in Firefox and Thunderbird to cause application crashes or execute arbitrary code by crafting websites that trigger unsafe state transitions during page reload operations.

CISA KEV Yes · 2022-03-283EPSS 0.69236 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.69236 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Mozilla, Firefox and Thunderbird. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious website that triggers onreadystatechange events during page reload cycles to destabilize the browser.
Business
Users experience browser crashes or unexpected termination of service, reducing productivity and user trust in the application.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the buffer overflow vulnerability in event handling to inject and execute arbitrary code within the browser process.
Business
Attackers gain code execution on user systems, enabling data theft, malware installation, and compromise of sensitive information stored in the browser.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mozilla (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mozillaCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.