CVE-2001-1144
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 · uneditedDirectory traversal vulnerability in McAfee ASaP VirusScan agent 1.0 allows remote attackers to read arbitrary files via a .. (dot dot) in the HTTP request.
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 · moderate confidenceThe McAfee ASaP VirusScan agent 1.0 contains a directory traversal vulnerability in its HTTP handling mechanism. Attackers can use '..' sequences in HTTP requests to navigate outside the intended web root directory and read arbitrary files on the system, potentially exposing sensitive configuration files, credentials, or other system data.
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= 1.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm McAfee ASaP VirusScan agent is installedLook for the McAfee ASaP VirusScan agent in your system programs list, services, or installed applications. On Windows, check Add/Remove Programs or the program directory (typically C:\Program Files\McAfee\ or similar).Affected if The application is present on the system
-
Identify the installed versionRight-click on the McAfee ASaP VirusScan agent icon or executable, select Properties, and check the Version tab. Alternatively, look in the installation directory for version information in files like version.txt, readme.txt, or the main executable's version resource.Affected if The version is exactly 1.0 (no other version is affected by this specific CVE)
-
Determine if HTTP remote management is enabledCheck if the HTTP service or remote management interface for the VirusScan agent is running. Look for a web server process listening on a port (commonly 80, 8080, or a McAfee-specific port) or check the agent configuration for remote HTTP access settings.Affected if The HTTP handling mechanism is active and accessible on the network
You are affected only if McAfee ASaP VirusScan agent version 1.0 is installed AND the HTTP remote management interface is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-provided patch or upgrade to a newer version of McAfee VirusScan that addresses this vulnerability. If the product is no longer supported, consider migrating to a current McAfee endpoint protection solution.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2001-1144 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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