Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-38153

Vulnerability in org.apache.kafka:kafka_2.11 (CVE-2021-38153)

Summary

Vulnerability in org.apache.kafka:kafka_2.11 (CVE-2021-38153). Confidential information can be exposed externally. Exploitable via Arrays.equals. Mitigation: upgrade to 2.8.1 or later.

Original description

The description as published by the source.

Some components in Apache Kafka use Arrays.equals to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful. Users should upgrade to 2.8.1 or higher, or 3.0.0 or higher where this vulnerability has been fixed. The affected versions include Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, and 2.8.0.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-38153 has been found in org.apache.kafka:kafka_2.11.
Attackers can target a specific entry point like Arrays.equals over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade org.apache.kafka:kafka_2.11 to 2.8.1 or later.
If unsure, ask your IT team or search "org.apache.kafka:kafka_2.11 CVE-2021-38153" on the vendor's site.

CVE-2021-38153 (org.apache.kafka:kafka_2.11) — CWE-203
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Arrays.equals
Patched: 2.8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-203) exists in org.apache.kafka:kafka_2.11. Attackers reach the vulnerable code path via Arrays.equals without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.kafka:kafka_2.11. Attack surface: Arrays.equals.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.8.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.kafka:kafka_2.11 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.kafka:kafka_2.11 to 2.8.1

    ステージング環境で 2.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.apache.kafka:kafka_2.11
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"last_affected":"2.4.1"}]}]
Maven org.apache.kafka:kafka_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"2.8.0"},{"fixed":"2.8.1"}]}]
Maven org.apache.kafka:kafka_2.13
[{"type":"ECOSYSTEM","events":[{"introduced":"2.8.0"},{"fixed":"2.8.1"}]}]
Maven org.apache.kafka:kafka-clients
[{"type":"ECOSYSTEM","events":[{"introduced":"2.8.0"},{"fixed":"2.8.1"}]}]
Bitnami kafka
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.6.3"},{"introduced":"2.7.0"},{"fixed":"2.7.2"},{"introduced":"2.8.0"},{"fixed":"2.8.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details