How severe is CVE-2014-2829?

No CVSS score has been assigned to CVE-2014-2829 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-2829?

CVE-2014-2829 affects the following packages: MongooseIM (Hex). Ecosystems affected: Hex.

How do I fix CVE-2014-2829?

Update MongooseIM to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2829 is resolved across your whole dependency graph.

How do I detect CVE-2014-2829 in my Hex dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for MongooseIM, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-2829 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2014-2829 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-2829, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-2829?

CVE-2014-2829 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-2829?

CVE-2014-2829 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-2829 published, and has it been updated?

CVE-2014-2829 was published on May 17, 2022 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💧 Hex

Not in CISA KEV

CVE-2014-2829 — MongooseIM

Fix: esl/MongooseIM@586d96c

CVE-2014-2829 is a CWE-264 vulnerability in MongooseIM. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for MongooseIM — see the affected versions and patch details below.

Erlang Solutions MongooseIM vulnerable to denial of service (DoS) via crafted XMPP stream

Published

May 17, 2022

Updated

Dec 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

💧MongooseIM

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

Erlang Solutions MongooseIM through 1.3.1 rev. 2 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💧Hex	`MongooseIM`	all versions	1.3.2`mix deps.update MongooseIM`

Affected Products

1 product · 5 configurations

Application

mongooseimerlang-solutions

≤ 1.3.1

4 versions

1.2.11.2.21.3.01.3.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Erlang Solutions MongooseIM through 1.3.1 rev. 2 does not properly restr…

github.comNVDApr 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for MongooseIM, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update MongooseIM to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2829 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-2829 in your dependencies?

Find it across Hex, including transitive dependencies.

Scan my dependencies How O3 SCA works