CVE-2008-2543
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 · uneditedThe ooh323 channel driver in Asterisk Addons 1.2.x before 1.2.9 and Asterisk-Addons 1.4.x before 1.4.7 creates a remotely accessible TCP port that is intended solely for localhost communication, and interprets some TCP application-data fields as addresses of memory to free, which allows remote attackers to cause a denial of service (daemon crash) via crafted TCP packets.
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 confidenceThe ooh323 channel driver in Asterisk Addons creates a TCP port intended for localhost-only communication but inadvertently exposes it to remote attackers. The driver improperly interprets TCP application-data fields as memory addresses to free, allowing remote attackers to send crafted packets that crash the daemon via invalid free operations.
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.2.0= 1.2.1= 1.2.2= 1.2.3= 1.2.4= 1.2.5= 1.2.6= 1.2.7= 1.2.8= 1.4.0= 1.4.1= 1.4.2CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 Asterisk Addons versionRun 'asterisk -V' or check package manager for asterisk-addons version (e.g., dpkg -l | grep asterisk-addons, rpm -qa | grep asterisk-addons)Affected if Version matches 1.2.0 through 1.2.8 or 1.4.0 through 1.4.2
-
Verify ooh323 module presenceCheck for the ooh323 channel driver module in the Asterisk modules directory (typically /usr/lib/asterisk/modules/) for files named chan_ooh323.so or similar, or run 'module show' in the Asterisk CLIAffected if The chan_ooh323 module exists and is available to be loaded
-
Confirm ooh323 module is loadedConnect to Asterisk CLI (asterisk -r) and run 'module show like ooh323' or check running processes for the moduleAffected if The ooh323 channel driver is currently loaded into memory
-
Check ooh323 TCP listener exposureRun 'netstat -tlnp | grep 33031' or 'ss -tlnp | grep 33031' to see if port 33031 (default ooh323 port) is listening, then verify binding address with 'asterisk -x "ooh323 show settings"' or similar commandAffected if Port 33031 is listening on a non-loopback interface (0.0.0.0 instead of 127.0.0.1) and is reachable from remote hosts
A system is affected if Asterisk Addons version falls within the vulnerable range AND the ooh323 module is loaded and its TCP port is exposed to network access.
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 Asterisk Addons to version 1.2.9 or 1.4.7 or later to obtain the patched ooh323 driver, or disable the ooh323 channel driver if not required.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2543 — 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-2008-2543 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