CVE-2002-0199
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 admin.cgi for Nullsoft Shoutcast Server 1.8.3 allows remote attackers to cause a denial of service and possibly execute arbitrary code via an argument with a large number of backslashes.
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 in admin.cgi for Nullsoft Shoutcast Server 1.8.3 allows remote attackers to cause denial of service and possibly execute arbitrary code via an argument containing a large number of backslashes.
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= 1.8.3CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Verify Shoutcast Server is installedCheck for Shoutcast Server process or installation directory. On Windows, look for sc_serv.exe process or check Program Files. On Linux/Unix, check for sc_serv binary in common locations like /usr/local/shoutcast or /opt/shoutcast.Affected if Shoutcast Server is not found on the system
-
Determine the installed Shoutcast versionLocate the sc_serv executable and run it with a version flag (typically sc_serv.exe -version or check the application log file at startup). Alternatively, check the server's HTTP response headers or the admin.cgi version information if accessible.Affected if The installed version is exactly 1.8.3
-
Confirm admin.cgi is accessibleAttempt to access admin.cgi via HTTP on the server's configured port (default 8000). For example, visit http://yourserver:8000/admin.cgi in a browser or use curl to request the endpoint.Affected if admin.cgi responds to HTTP requests (returns 200 or 401/403 error rather than connection refused)
-
Check if the server is exposed to networkReview firewall rules, router port forwarding, or cloud security groups to determine if the Shoutcast web interface port (default 8000) is open to untrusted networks or the internet.Affected if Port 8000 (or the configured Shoutcast port) is accessible from untrusted networks
The environment is affected if Shoutcast Server version 1.8.3 is running and admin.cgi is network-accessible, since the buffer overflow can be triggered by sending a request with many backslash characters.
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 dataUpgrade Shoutcast Server to the latest version which includes patched admin.cgi; if unable to upgrade, restrict access to admin.cgi via network segmentation or authentication.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0199 — 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-2002-0199 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