Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2001-0205: Directory Traversal in AOLserver 3.2 and earlier

Published Mar 9, 2001 · 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
EPSS23.6%98th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Aol
IdentifiersCVE-2001-0205CWE-22

AOLserver 3.2 and earlier are vulnerable to a directory traversal attack that allows remote attackers to read arbitrary files on the server. The vulnerability is due to improper sanitization of user-supplied input in the requested pathname, where the sequence "..." can be used as a variant of the classic ".." (dot dot) to traverse directories outside the web root.

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 attackers to read arbitrary files on the server, potentially exposing sensitive information such as configuration files, credentials, or application source code. This can lead to further compromise of the system or sensitive data leakage.

Mitigation

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

As an interim mitigation, implement input validation and filtering to reject or sanitize any pathnames containing suspicious sequences such as ".." or "...". Restrict file access permissions on the server to limit the impact of a successful attack.

Remediation

Patch, then assume compromise.

Upgrade to a version of AOLserver later than 3.2 where this input validation issue is fixed. Ensure that all user-supplied pathnames are properly sanitized to prevent directory traversal attacks.

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

Frequently asked questions

Is CVE-2001-0205 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2001-0205 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2001-0205?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2001-0205.
Is there a patch for CVE-2001-0205?
Upgrade to a version of AOLserver later than 3.2 where this input validation issue is fixed. Ensure that all user-supplied pathnames are properly sanitized to prevent directory traversal attacks.
What products are affected by CVE-2001-0205?
Aolserver.
How severe is CVE-2001-0205?
CVE-2001-0205 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 23.6% (98th 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.