Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2008-7244: Printing DoS in Mozilla Firefox via window.print Loop

Published Sep 18, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS4.5%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Mozilla
IdentifiersCVE-2008-7244CWE-400

A vulnerability in Mozilla Firefox 3.0.1 and earlier allows remote attackers to cause a denial of service by repeatedly invoking the window.print function in a loop. This results in the browser hanging, effectively making it unresponsive to user input. The issue is triggered by JavaScript code that continuously calls window.print, overwhelming the browser's print dialog handling.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation leads to a denial of service condition where the browser becomes unresponsive, requiring the user to forcibly terminate the process. There is no evidence of code execution or data compromise, but it can disrupt user activity and potentially be used in nuisance attacks.

Mitigation

If you can’t patch tonight, do this now.

Disable JavaScript or restrict execution of untrusted scripts. Use browser extensions or security settings to limit or prompt for repeated calls to window.print. Consider deploying content security policies to reduce exposure to malicious scripts.

Remediation

Patch, then assume compromise.

Upgrade to a version of Mozilla Firefox where this issue is resolved. Later versions include mitigations to prevent abuse of the window.print function from JavaScript loops.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MozillaFirefoxapplication
FAQ

Frequently asked questions

Is CVE-2008-7244 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-7244 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-7244?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2008-7244.
Is there a patch for CVE-2008-7244?
Upgrade to a version of Mozilla Firefox where this issue is resolved. Later versions include mitigations to prevent abuse of the window.print function from JavaScript loops.
What products are affected by CVE-2008-7244?
Mozilla Firefox.
How severe is CVE-2008-7244?
CVE-2008-7244 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 4.5% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.