Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2009-0645: Directory Traversal in Jaws 0.8.8 index.php

Published Feb 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.
CVSS6.5Medium · v2
EPSS6.3%94th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Jaws
IdentifiersCVE-2009-0645CWE-22 · Improper Limitation of a Pathname…

A directory traversal vulnerability exists in index.php of Jaws 0.8.8, where remote authenticated users can read arbitrary files on the server by supplying directory traversal sequences (..) in the 'language', 'Introduction_complete', and 'use_log' parameters. This vulnerability is distinct from CVE-2004-2445 and allows attackers to access files outside the intended directory scope.

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 allows remote authenticated users to read arbitrary files on the server filesystem, potentially exposing sensitive information such as configuration files, credentials, or other data not intended for user access.

Mitigation

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

Restrict access to the application to trusted users only, monitor logs for suspicious parameter usage, and employ web application firewalls (WAFs) to block directory traversal attempts as an interim measure until a patch is applied.

Remediation

Patch, then assume compromise.

Upgrade to a version of Jaws where input validation and sanitization is properly implemented for the affected parameters, ensuring that directory traversal sequences are not permitted. Apply any vendor-supplied patches addressing this issue.

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
JawsJawsapplication
FAQ

Frequently asked questions

Is CVE-2009-0645 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-0645 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-0645?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2009-0645.
Is there a patch for CVE-2009-0645?
Upgrade to a version of Jaws where input validation and sanitization is properly implemented for the affected parameters, ensuring that directory traversal sequences are not permitted. Apply any vendor-supplied patches addressing this issue.
What products are affected by CVE-2009-0645?
Jaws.
How severe is CVE-2009-0645?
CVE-2009-0645 has a CVSS v2 score of 6.5 (Medium) and an EPSS score of 6.3% (94th 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.