CVE-2014-2745
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 · uneditedProsody before 0.9.4 does not properly restrict the processing of compressed XML elements, which allows remote attackers to cause a denial of service (resource consumption) via a crafted XMPP stream, aka an "xmppbomb" attack, related to core/portmanager.lua and util/xmppstream.lua.
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 confidenceProsody before 0.9.4 fails to properly restrict the processing of compressed XML elements in XMPP streams. Remote attackers can send crafted XMPP streams containing deeply nested or highly repetitive compressed XML that causes excessive memory and CPU consumption, resulting in denial of service.
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<= 0.9.3= 0.1.0= 0.2.0= 0.3.0= 0.4.0= 0.4.1= 0.4.2= 0.5.0= 0.5.1= 0.5.2= 0.6.0= 0.6.1CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check installed Prosody versionRun `prosodyctl version` or check your package manager for the installed prosody package versionAffected if Version is 0.9.3 or earlier, or matches versions 0.1.0 through 0.6.1 listed in affected versions
-
Locate Prosody configuration fileOpen the Prosody configuration file, typically located at /etc/prosody/prosody.cfg.luaAffected if Configuration file exists and the server is running
-
Verify if stream compression is enabledIn the configuration file, search for modules_enabled or specifically look for 'compress' or 'zlib' module entries in the modules list, or check for `compression` settings under the global or vhost sectionAffected if Stream compression (compress/zlib module) is listed as enabled in the modules section or compression settings are present and active
-
Confirm the vulnerability conditionCompare your findings: if Prosody version is <= 0.9.3 AND stream compression module is enabled, the environment is vulnerable to the DoS attack via crafted compressed XML elementsAffected if Both conditions are true: version is affected AND compression feature is in use
A system is affected if it runs Prosody version 0.9.3 or earlier (including 0.1.0 through 0.6.1) AND has stream compression enabled in the configuration, allowing remote attackers to trigger excessive resource consumption via crafted compressed XML streams.
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 Prosody to version 0.9.4 or later to patch the vulnerability. Additionally, implement rate limiting and connection thresholds on XMPP traffic as a defense-in-depth measure.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2745 — 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-2014-2745 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