CVE-2002-0464
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 Hosting Controller 1.4.1 and earlier allows remote attackers to read and modify arbitrary files and directories via a .. (dot dot) in arguments to (1) file_editor.asp, (2) folderactions.asp, or (3) editoractions.asp.
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 · high confidenceDirectory traversal vulnerability in Hosting Controller 1.4.1 and earlier allows remote attackers to read and modify arbitrary files via '..' sequences in arguments to file_editor.asp, folderactions.asp, and editoractions.asp. The vulnerability stems from insufficient input validation on path parameters in these ASP files.
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.4= 1.4.1CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Identify Hosting Controller installation and versionLocate the Hosting Controller installation directory and check the version information, typically found in the application metadata, installer records, or the main executable/dll version properties. Compare the installed version against the affected range (1.4 and 1.4.1).Affected if The installed version is 1.4, 1.4.1, or any earlier version.
-
Locate vulnerable ASP files on the serverSearch the web root directory for the files file_editor.asp, folderactions.asp, and editoractions.asp. These are typically found in the Hosting Controller web administration interface path.Affected if Any of these three ASP files exist on the server.
-
Verify web accessibility of vulnerable pagesCheck if the identified ASP files are accessible via HTTP/HTTPS from the web server. Attempt to access these endpoints with a web browser or curl command to confirm they respond.Affected if The vulnerable ASP files are accessible over the network without authentication or with valid authentication.
-
Inspect input validation on path parametersReview the source code of file_editor.asp, folderactions.asp, and editoractions.asp to verify whether the application properly validates and sanitizes path parameters, specifically checking for rejection of '..' sequences.Affected if The ASP files lack proper input validation for '..' sequences in path parameters.
A user is affected if Hosting Controller version 1.4 or earlier is installed and the vulnerable ASP files (file_editor.asp, folderactions.asp, editoractions.asp) are accessible without proper input validation for directory traversal sequences.
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 vendor patch if available, or implement input validation to reject '..' sequences in URL parameters at the web application firewall or application layer. Restrict file system permissions to limit the impact of traversal attempts.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0464 — 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-2002-0464 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