CVE-2017-12610

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.

Published: 2018-07-26 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-12610 is rated Moderate Risk (59.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.99%). EPSS rose +2.30% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-12610

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.68% 2.99% +2.30%
2 2026-04-28 0.37% 0.68% +0.31%
3 2026-03-13 — 0.37% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-12610

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 5.2 [email protected]
4.9 2.0 MEDIUM
AV:N/AC:M/Au:S/C:P/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 6.8 4.9 [email protected]

Weakness enumeration for CVE-2017-12610

GitHub Security Advisory for CVE-2017-12610

GHSA-xm78-4m3g-7wm7 · Severity: medium · Ecosystem: maven — Improper Authentication in Apache Kafka

OS Trackers for CVE-2017-12610

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2017-12610

Affected software / configurations for CVE-2017-12610

Vendor Product Version Raw CPE
apache kafka >= 0.10.0.0, <= 0.10.2.1 cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*
apache kafka >= 0.11.0.0, <= 0.11.0.1 cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*

References for CVE-2017-12610

cvelogic Threat Intelligence