CVE-1999-0360
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 · uneditedMS Site Server 2.0 with IIS 4 can allow users to upload content, including ASP, to the target web site, thus allowing them to execute commands remotely.
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 confidenceMS Site Server 2.0 with IIS 4 contains an authenticated file upload vulnerability where users with upload permissions can upload arbitrary file types, including ASP scripts, to the web server. Requesting these uploaded ASP files allows remote command execution with the web server's privileges.
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= 2.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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Confirm Site Server 2.0 installationCheck the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Site Server\2.0 under the install path, or inspect Program Files\Site Server for the existence of the Site Server binaries.Affected if The registry key exists or the Site Server 2.0 directory is present on the system.
-
Verify upload functionality is enabledExamine the Site Server administration interface or configuration files for the Content Management component. Look for upload/upload capabilities settings in the Site Server MMC snap-in or via the smsaadmin utility.Affected if The upload feature is configured and accessible to authenticated users.
-
Identify web-accessible upload directoriesLocate directories configured for user uploads in Site Server. These are typically found under the wwwroot\upload or similar paths configured in the Site Server Content Management settings.Affected if Upload directories exist and are accessible via HTTP through IIS.
-
Check for unexpected ASP files in upload directoriesUse the file system to enumerate .asp files within the identified upload directories. If IIS script execution is enabled on these directories, these uploaded ASP files would be executable.Affected if Any .asp files exist in web-accessible upload directories, indicating arbitrary script upload was possible.
-
Confirm script execution permissions on upload directoriesIn IIS Manager, examine the properties of upload directories. Check the Execute Permissions setting under the Home Directory or Directory tab - verify if 'Scripts and Executables' or 'Scripts only' is enabled.Affected if Script execution permissions are granted to upload directories, allowing uploaded ASP files to run.
If Site Server 2.0 is installed with upload functionality enabled and script execution permissions exist on upload directories, the system is vulnerable to remote command execution via uploaded ASP scripts.
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 dataRestrict or disable the content upload functionality in Site Server 2.0, implement strict allowlist-based file type validation on upload directories, remove script execution permissions from upload directories, or migrate to supported Microsoft web platform technologies.
- Consultation8.0 h
- Implementation24.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0360 — 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-0360 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