PatchTheCVEjabberd2 vulnerabilities and fixes
Recent CVEs affecting jabberd2, with upgrade or downgrade steps. 3 tracked.
jabberd2 has 3 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2018-03-12. Highest priority: CVE-2017-10807 (score 61/100).
- CVE-2017-18226 MEDIUM 5.5 UPGRADE The Gentoo net-im/jabberd2 package through 2.6.1 sets the ownership of /var/run/jabber to the jabber account,
- CVE-2017-18225 HIGH 7.8 UPGRADE The Gentoo net-im/jabberd2 package through 2.6.1 installs jabberd, jabberd2-c2s, jabberd2-router, jabberd2-s2s
- CVE-2017-10807 CRITICAL 9.8 UPGRADE JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl
FAQ
How do I fix jabberd2 vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is jabberd2 being exploited right now?
None of the tracked jabberd2 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jabberd2 CVE should I patch first?
CVE-2017-10807 currently ranks highest (61/100): JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl.