# CVE-2017-12610: Improper Authentication in Apache Kafka

> Authenticated clients can impersonate other users via crafted protocol messages in Apache Kafka's SASL implementations, leading to unauthorized access.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xm78-4m3g-7wm7

## What is CVE-2017-12610?

CVE-2017-12610 is a medium-severity authentication bypass vulnerability in Apache Kafka, published on 26 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Apache Kafka 0.10.0.0 to 0.10.2.1 and 0.11.0.0 to 0.11.0.1, authenticated Kafka clients may use impersonation via a manually crafted protocol message with SASL/PLAIN or SASL/SCRAM authentication when using the built-in PLAIN or SCRAM server implementations in Apache Kafka.

Weakness: CWE-287 (Improper Authentication)

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

4 open source packages ship an affected version, including org.apache.kafka:kafka-clients. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.kafka:kafka-clients` | Maven | From 0.10.0.0 | 0.10.2.2 |
| `org.apache.kafka:kafka-clients` | Maven | From 0.10.0.0 | 0.10.2.2 |
| `org.apache.kafka:kafka-clients` | Maven | From 0.11.0.0 | 0.11.0.2 |
| `org.apache.kafka:kafka-clients` | Maven | From 0.11.0.0 | 0.11.0.2 |

Products: Apache Kafka.

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

Upgrade org.apache.kafka:kafka-clients to a fixed version for your release line: 0.10.2.2 or 0.11.0.2.

## Is CVE-2017-12610 being exploited?

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

## Other vulnerabilities in Apache Kafka

- [CVE-2026-33557](https://insights.sbomify.com/CVE-2026-33557/): Apache Kafka: Missing JWT token validation in OAUTHBEARER authentication (critical 9.1)
- [CVE-2025-27818](https://insights.sbomify.com/CVE-2025-27818/): Apache Kafka: Possible RCE attack via SASL JAAS LdapLoginModule configuration (high 8.8)
- [CVE-2018-17196](https://insights.sbomify.com/CVE-2018-17196/): Improper Input Validation in Apache Kafka (high 8.8)
- [CVE-2026-35554](https://insights.sbomify.com/CVE-2026-35554/): Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition (high 8.7)
- [CVE-2025-27817](https://insights.sbomify.com/CVE-2025-27817/): Apache Kafka Client: Arbitrary file read and SSRF vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12610 is a medium-severity authentication bypass vulnerability in Apache Kafka, published on 26 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12610 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.kafka:kafka-clients (Maven): affected from 0.10.0.0; fixed in 0.10.2.2
- org.apache.kafka:kafka-clients (Maven): affected from 0.10.0.0; fixed in 0.10.2.2
- org.apache.kafka:kafka-clients (Maven): affected from 0.11.0.0; fixed in 0.11.0.2
- org.apache.kafka:kafka-clients (Maven): affected from 0.11.0.0; fixed in 0.11.0.2

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-12610/ (Markdown: https://insights.sbomify.com/CVE-2017-12610/index.md)
```

## Sources

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

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