CVE-2001-1229
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 overflows in (1) Icecast before 1.3.9 and (2) libshout before 1.0.4 allow remote attackers to cause a denial of service (crash) and execute arbitrary code.
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 vulnerabilities in Icecast streaming server (versions before 1.3.9) and libshout library (versions before 1.0.4) allow remote unauthenticated attackers to crash the service via buffer overflow and potentially execute arbitrary code. The vulnerability stems from insufficient bounds checking when handling streaming requests.
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.3.9<= 1.0.4CVSS 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.
-
Identify Icecast installation and versionRun 'icecast --version' or check the icecast binary with 'file icecast' and examine any version string in the binary. Check installed packages via package manager (dpkg -l icecast, rpm -qa | grep icecast) or look for icecast in /usr/bin/, /usr/local/bin/, or /opt/.Affected if Icecast version is 1.3.9 or lower, or no version can be determined but icecast binary exists.
-
Identify libshout installation and versionRun 'shout-config --version' if shout utility exists, or check library files in /usr/lib/ for libshout.so* files and examine their metadata. Check package manager for libshout packages.Affected if libshout version is 1.0.4 or lower, or libshout library files exist without version information.
-
Confirm Icecast service is runningRun 'ps aux | grep icecast' or 'ps -ef | grep icecast' to list running icecast processes. Also check for listening ports with 'netstat -tlnp | grep 8000' (Icecast default port) or 'ss -tlnp | grep 8000'.Affected if Icecast server process is actively running and listening on network ports.
-
Verify network exposureCheck /etc/icecast.xml configuration file for <listen-socket> bind address settings. Run 'netstat -tlnp' or 'ss -tlnp' to see which IP addresses and ports Icecast is bound to. Inspect firewall rules with 'iptables -L' to determine if the service is accessible from untrusted networks.Affected if Icecast is bound to 0.0.0.0 or an externally accessible IP and firewall allows inbound connections.
-
Check for streaming request handlersExamine icecast configuration file (typically /etc/icecast.xml or /etc/icecast/icecast.xml) for <mount> definitions and source client configurations. Verify if public streaming is enabled.Affected if Icecast is configured to accept source connections or client requests from the network, making the buffer overflow triggerable.
You are affected if Icecast version 1.3.9 or lower, or libshout version 1.0.4 or lower is installed and the service is running and network-accessible.
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 to Icecast 1.3.9 or later and libshout 1.0.4 or later. If these legacy versions cannot be upgraded due to system constraints, consider migrating to modern streaming server solutions or implementing network-level access controls to limit exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1229 — 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-2001-1229 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