CVE-2011-1755

CVE-2011-1755 is a high-severity vulnerability in Jabberd2 with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-776.

Key facts

Description

jabberd2 before 2.2.14 does not properly detect recursion during entity expansion, which allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted XML document containing a large number of nested entity references, a similar issue to CVE-2003-1564.

Frequently asked questions

What is CVE-2011-1755?
jabberd2 before 2.2.14 does not properly detect recursion during entity expansion, which allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted XML document containing a large number of nested entity references, a similar issue to CVE-2003-1564.
How severe is CVE-2011-1755?
CVE-2011-1755 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2011-1755 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2011-1755?
CVE-2011-1755 primarily affects Jabberd2. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2011-1755?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2011-1755 published?
CVE-2011-1755 was published on 2011-06-21 and last updated on 2026-06-16.

References

Affected products (6)

More vulnerabilities in Jabberd2

All CVEs affecting Jabberd2 →

Other CWE-776 vulnerabilities

Browse all CWE-776 vulnerabilities →