# CVE-2017-10807: Auth bypass in n/a

> Attackers can authenticate anonymously to JabberD servers even when anonymous SASL is disabled, bypassing intended access controls.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-10807, DSA-3902-1, GHSA-cv95-3vq8-8f64, SUSE-SU-2017:2266-1, SUSE-SU-2017:2267-1, UBUNTU-CVE-2017-10807

## What is CVE-2017-10807?

CVE-2017-10807 is a critical authentication bypass vulnerability in n/a, published on 4 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-10807?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jabberd` | SUSE:Manager Proxy 3.0 | All versions | 2.6.1-4.6.1 |
| `jabberd` | SUSE:Manager Proxy 3.1 | All versions | 2.6.1-3.3.1 |
| `osad` | SUSE:Manager Proxy 3.1 | All versions | 5.11.80.3-2.3.1 |
| `rhnpush` | SUSE:Manager Proxy 3.1 | All versions | 5.5.104.3-2.3.2 |
| `spacewalk-backend` | SUSE:Manager Proxy 3.1 | All versions | 2.7.73.7-2.3.1 |
| `spacewalk-certs-tools` | SUSE:Manager Proxy 3.1 | All versions | 2.7.0.7-2.3.1 |
| `spacewalk-proxy` | SUSE:Manager Proxy 3.1 | All versions | 2.7.1.4-2.3.1 |
| `spacewalk-web` | SUSE:Manager Proxy 3.1 | All versions | 2.7.1.10-2.3.1 |
| `spacewalksd` | SUSE:Manager Proxy 3.1 | All versions | 5.0.26.3-2.3.1 |
| `supportutils-plugin-susemanager-client` | SUSE:Manager Proxy 3.1 | All versions | 3.1.2-2.3.1 |
| `zypp-plugin-spacewalk` | SUSE:Manager Proxy 3.1 | All versions | 0.9.16-2.3.1 |
| `jabberd` | SUSE:Manager Server 3.0 | All versions | 2.6.1-4.6.1 |

Products: Jabberd2 Jabberd2.

## How do I fix CVE-2017-10807?

Upgrade to a fixed version.

## Is CVE-2017-10807 being exploited?

There is no known exploitation of CVE-2017-10807 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-18225](https://insights.sbomify.com/CVE-2017-18225/): Privilege escalation in n/a (high 7.8)
- [CVE-2015-2058](https://insights.sbomify.com/CVE-2015-2058/): Information disclosure in n/a (medium 6.5)
- [CVE-2017-18226](https://insights.sbomify.com/CVE-2017-18226/): Privilege escalation in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10807 and fix it if it is affected.

What it is: CVE-2017-10807 is a critical authentication bypass vulnerability in n/a, published on 4 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10807 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-10807/ (Markdown: https://insights.sbomify.com/CVE-2017-10807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-10807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10807
- OSV: https://osv.dev/vulnerability/CVE-2017-10807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-10807/
Summaries are generated and may contain mistakes; the official description above is the record.