Command execution via enabled SSI #exec directives
Published Feb 4, 2000 · Updated Aug 1, 2024
Enabled SSI #exec in Microsoft Internet Information Services (IIS) allows attackers to execute server-side programs via SSI files. The SSI interpreter processes #exec directives in mapped SSI files as application or shell-command requests and returns their output to the browser. Execution requires enabled #exec processing and an attacker-controlled directive or an exposed SSI page that invokes a program; the record does not specify an injection path or affected versions.
Summary
What happened
Enabled SSI #exec in Microsoft Internet Information Services (IIS) allows attackers to execute server-side programs via SSI files. The SSI interpreter processes #exec directives in mapped SSI files as application or shell-command requests and returns their output to the browser. Execution requires enabled #exec processing and an attacker-controlled directive or an exposed SSI page that invokes a program; the record does not specify an injection path or affected versions.
The record
- CVE
- CVE-1999-0561
- Published
- Feb 4, 2000
- Updated
- Aug 1, 2024
- Vendor
- Microsoft Corporation
- Product
- Internet Information Services (IIS)
- Classifications
- T1059.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2000CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us