CVE-2000-0122
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 · uneditedFrontpage Server Extensions allows remote attackers to determine the physical path of a virtual directory via a GET request to the htimage.exe CGI program.
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 confidenceFrontPage Server Extensions contains a path disclosure vulnerability in the htimage.exe CGI program. Remote attackers can send a GET request to this executable and receive the physical path of virtual directories on the server, revealing sensitive filesystem information that could aid further attacks.
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= 98= 2000CVSS 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.
-
Locate htimage.exe CGI programSearch the web server filesystem for htimage.exe, typically in directories such as /_vti_bin/, /cgi-bin/, or /scripts/. Use file system search commands like 'find' or directory listing to locate this file.Affected if htimage.exe file exists in any web-accessible CGI directory on the server
-
Verify FrontPage Server Extensions installationCheck if Microsoft FrontPage Server Extensions are installed on the web server. Look for FrontPage-related directories such as /_vti_bin, /_vti_cnf, or /_vti_pvt, and check for frontpg.ini or other FrontPage configuration files.Affected if FrontPage Server Extensions are installed and the htimage.exe CGI program is present
-
Confirm FrontPage versionCheck the installed FrontPage version by examining version information in the FrontPage binaries, DLLs, or associated configuration files. Look for version identifiers indicating 98 or 2000.Affected if The installed FrontPage version is 98 or 2000 (exact versions as specified in affected products)
-
Test for path disclosure vulnerabilitySend a crafted GET request to htimage.exe via HTTP, such as 'GET /_vti_bin/htimage.exe? HTTP/1.1' or similar malformed request, and observe whether the server response reveals physical file system paths.Affected if The server response contains physical directory paths or file system information that should not be publicly disclosed
The server is affected if htimage.exe is present, FrontPage 98 or 2000 Server Extensions are installed, and the CGI program responds with path information to crafted requests.
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 dataDisable or remove the htimage.exe CGI program from the server, or update FrontPage Server Extensions to a patched version if available. Alternatively, configure the web server to prevent path disclosure from CGI scripts.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0122 — 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-2000-0122 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