CVE-1999-1376
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 · uneditedBuffer overflow in fpcount.exe in IIS 4.0 with FrontPage Server Extensions allows remote attackers to execute arbitrary commands.
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 confidenceBuffer overflow vulnerability in fpcount.exe, a FrontPage hit counter component included with FrontPage Server Extensions on IIS 4.0. The overflow allows remote attackers to execute arbitrary commands by sending specially crafted input to the vulnerable executable.
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= 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check IIS versionOpen IIS Manager, right-click on the server, select Properties, and check the version under 'Internet Information Services' or run 'iisreset' /status or check the Windows version and IIS installationAffected if The system is running IIS version 4.0 specifically. Earlier versions (IIS 3.0) or later versions (IIS 5.0+) are not affected by this specific CVE.
-
Locate fpcount.exeSearch for fpcount.exe in the web root directories and Scripts folders. Typical paths include C:\Inetpub\Scripts\fpcount.exe or C:\Program Files\Common Files\Microsoft Shared\web server extensions\...\fpcount.exeAffected if fpcount.exe exists on the server. If it does not exist, the vulnerability cannot be exploited.
-
Check if FrontPage Server Extensions are installedLook for the FrontPage Server Extensions installation directories (webext5.dll, fpsrvadm.exe, or check Add/Remove Programs for Microsoft FrontPage Server Extensions)Affected if FrontPage Server Extensions are installed. The vulnerability is present in the fpcount.exe component bundled with these extensions on IIS 4.0.
-
Verify fpcount.exe is accessible via webAttempt to access fpcount.exe through a browser (e.g., http://yourserver/scripts/fpcount.exe or check IIS script mappings for .exe extensions). Check IIS Manager under 'Home Directory' > 'Configuration' > 'App Mappings'Affected if The executable is mapped in IIS script mappings and reachable via HTTP/HTTPS. Without web accessibility, remote exploitation is not possible.
A system is affected only if it runs IIS 4.0 with FrontPage Server Extensions installed and fpcount.exe present and accessible via the web server.
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 dataRemove or disable the fpcount.exe component from IIS 4.0, apply Microsoft's security patches for FrontPage Server Extensions, or migrate to supported IIS versions with current FrontPage extensions.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1376 — 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-1999-1376 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