CVE-2000-0114
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 name of the anonymous account via an RPC POST request to shtml.dll in the /_vti_bin/ virtual directory.
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 confidenceFrontpage Server Extensions contains an information disclosure vulnerability where remote attackers can determine the name of the anonymous account by sending a crafted RPC POST request to shtml.dll in the /_vti_bin/ virtual directory. This enumerated account name can then be used for further targeted 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= 3.0= 4.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.
-
Identify IIS versionCheck the IIS version installed on the system. For IIS 4.0, open IIS Manager, right-click the server, and select Properties. For command-line, check the registry key HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersion or examine the file version of w3svc.dll in system32/inetsrv.Affected if The installed version is 3.0 or 4.0 exactly.
-
Verify Frontpage Server Extensions are installedCheck for the presence of Frontpage Server Extensions by looking for the _vti_bin virtual directory in IIS or searching for fpsrvadm.exe or fpadmin.exe in the system path. Also check for _vti_inf.html in the web root directories.Affected if Frontpage Server Extensions are installed on the IIS server.
-
Confirm /_vti_bin/ virtual directory existsIn IIS Manager, expand the default website and look for a virtual directory named _vti_bin. Alternatively, attempt to access http://yourserver/_vti_bin/ via a web browser - a 403 or directory listing response indicates it exists.Affected if The /_vti_bin/ virtual directory is present and accessible.
-
Check for shtml.dll in /_vti_bin/Attempt to access http://yourserver/_vti_bin/shtml.dll or examine the physical path of the _vti_bin virtual directory and verify shtml.dll exists in that folder.Affected if shtml.dll is present in the /_vti_bin/ directory and accessible via HTTP.
-
Verify anonymous authentication is enabledIn IIS Manager, right-click the _vti_bin directory, select Properties, and check the Directory Security tab. Under Authentication Methods, verify that Anonymous Access is enabled and note the anonymous user account (typically IUSR_<machinename>).Affected if Anonymous access is enabled for the /_vti_bin/ virtual directory.
The environment is affected if running IIS 3.0 or 4.0 with Frontpage Server Extensions installed, where the /_vti_bin/ virtual directory containing shtml.dll is present and accessible with anonymous authentication enabled.
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 /_vti_bin/ virtual directory if Frontpage Server Extensions are not required. If needed, apply all available patches or migrate to a supported web publishing solution.
- 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-0114 — 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-0114 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