CVE-1999-0348
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 · uneditedIIS ASP caching problem releases sensitive information when two virtual servers share the same physical 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 · low confidenceIn Microsoft IIS with ASP, when two or more virtual servers share the same physical directory path on the server, an ASP caching flaw can cause sensitive information from one virtual server to be inadvertently disclosed to requests from another virtual server sharing that directory.
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
- 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 IIS versionOpen Internet Services Manager (ism.dll) or check the Windows registry key HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersion, or run 'iisweb.vbs /query' if availableAffected if The installed version is Microsoft IIS 4.0
-
Verify ASP is enabledCheck if ASP (Active Server Pages) is installed by looking for the asp.dll file in the system32 directory, or check IIS Web Service Extensions to see if 'Active Server Pages' is allowedAffected if ASP is installed and enabled on the IIS server
-
List all virtual serversOpen Internet Services Manager, right-click on the web site root, and select 'Properties' to view the website, or use the command 'cscript adsutil.vbs enum /p w3svc' to enumerate sitesAffected if Multiple virtual servers (websites) are configured on the IIS instance
-
Check for shared physical directoriesFor each virtual server, note its 'Home Directory' physical path in IIS properties. Compare these paths across all virtual servers to identify any that share the same physical directory on the server's filesystemAffected if Two or more virtual servers have their Home Directory pointing to identical physical folder paths
The environment is affected if running IIS 4.0 with ASP enabled and two or more virtual servers share the same physical directory path, which could cause cached ASP content from one virtual server to leak to requests from another.
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 dataAvoid configuring multiple virtual servers to point to the same physical directory. Ensure each virtual server has an isolated physical directory path, or apply relevant IIS/ASP security patches from the era and consider migrating to modern IIS versions.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0348 — 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-0348 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