CVE-2017-10807: JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl

Q: How do I fix CVE-2017-10807?

jabberd2: upgrade to newer than 2.6.0. Exact commands for each OS are on this page.

Q: Is CVE-2017-10807 being exploited?

CVE-2017-10807 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-10807 affect?

CVE-2017-10807 affects jabberd2. Severity is critical (CVSS 9.8). JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl.anonymous c2s.xml option is not enabled.

Q: How urgent is CVE-2017-10807?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2017-10807 is a critical-severity flaw (CVSS 9.8) affecting jabberd2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl.anonymous c2s.xml option is not enabled.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.8% (top 13%)
CISA exploited list	No
Weakness	CWE-287
Published	2017-07-04
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jabberd2

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-07-04 15:29 UTCPublished CVE record published
2026-06-17 01:00 UTCUpdated Record last modified

jabberd2 jabberd2 UPGRADE

Affected: <= 2.6.0

Fixed in: newer than 2.6.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jabberd2 || rpm -q jabberd2 || jabberd2 --version

2. UPGRADE to newer than 2.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jabberd2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jabberd2

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-10807?

jabberd2: upgrade to newer than 2.6.0. Exact commands for each OS are on this page.

Is CVE-2017-10807 being exploited?

CVE-2017-10807 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-10807 affect?

CVE-2017-10807 affects jabberd2. Severity is critical (CVSS 9.8). JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl.anonymous c2s.xml option is not enabled.

How urgent is CVE-2017-10807?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

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

References

← Back to latest CVEs