CVE-2021-38153: Timing Attack Vulnerability for Apache Kafka Connect and Clients

Published Sep 21, 2021
·
Updated

Apache Kafka could allow a remote attacker to obtain sensitive information, caused by a timing attack flaw due to the use of "Arrays.equals" to validate a password or key. By utilizing brute-force attack techniques, an attacker could exploit this vulnerability to obtain credentials information, and use this information to launch further attacks against the affected system.

Other sources

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.

Affected Software

34 affected componentsFixes available
maven/org.apache.kafka:kafka-clients=2.8.0
2.8.1
maven/org.apache.kafka:kafka-clients>=2.7.0<2.7.2
2.7.2
maven/org.apache.kafka:kafka-clients>=2.0.0<2.6.3
2.6.3
maven/org.apache.kafka:kafka_2.13=2.8.0
2.8.1
maven/org.apache.kafka:kafka_2.13>=2.7.0<2.7.2
2.7.2
maven/org.apache.kafka:kafka_2.13>=2.4.0<2.6.3
2.6.3
maven/org.apache.kafka:kafka_2.12>=2.0.0<2.6.3
2.6.3
maven/org.apache.kafka:kafka_2.11>=2.0.0<=2.4.1
redhat/kafka-2.8.1 kafka-clients<2.8.1
2.8.1
IBM Cognos Analytics<=12.0.0-12.0.3
IBM Cognos Analytics<=11.2.0-11.2.4 FP4
Apache Kafka>=2.0.0<2.6.3
Apache Kafka>=2.7.0<2.7.2
Apache Kafka=2.8.0
quarkus quarkus<2.2.4
Oracle Communications Brm - Elastic Charging Engine<12.0.0.4.6
Oracle Communications Brm - Elastic Charging Engine=12.0.0.5.0
Oracle Communications Cloud Native Core Policy=1.15.0
Oracle Financial Services Analytical Applications Infrastructure>=8.0.6.0<=8.0.9.0
Oracle Financial Services Analytical Applications Infrastructure>=8.1.0.0.0<=8.1.20
Oracle Financial Services Behavior Detection Platform>=8.0.6.0.0<=8.0.8.0
Oracle Financial Services Behavior Detection Platform=8.1.1.0
Oracle Financial Services Behavior Detection Platform=8.1.1.1
Oracle Financial Services Behavior Detection Platform=8.1.2.0
Oracle Financial Services Enterprise Case Management=8.0.7.1
Oracle Financial Services Enterprise Case Management=8.0.7.2
Oracle Financial Services Enterprise Case Management=8.0.8.0
Oracle Financial Services Enterprise Case Management=8.0.8.1
Oracle Financial Services Enterprise Case Management=8.1.1.0
Oracle Financial Services Enterprise Case Management=8.1.1.1
Oracle Primavera Unifier=18.8
Oracle Primavera Unifier=19.12
Oracle Primavera Unifier=20.12
Oracle Primavera Unifier=21.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.kafka:kafka-clients to a version that resolves this vulnerability.

    Fixed in 2.8.1
  2. Upgrade

    Upgrade maven/org.apache.kafka:kafka-clients to a version that resolves this vulnerability.

    Fixed in 2.7.2
  3. Upgrade

    Upgrade maven/org.apache.kafka:kafka-clients to a version that resolves this vulnerability.

    Fixed in 2.6.3
  4. Upgrade

    Upgrade maven/org.apache.kafka:kafka_2.13 to a version that resolves this vulnerability.

    Fixed in 2.8.1
  5. Upgrade

    Upgrade maven/org.apache.kafka:kafka_2.13 to a version that resolves this vulnerability.

    Fixed in 2.7.2
  6. Upgrade

    Upgrade maven/org.apache.kafka:kafka_2.13 to a version that resolves this vulnerability.

    Fixed in 2.6.3
  7. Upgrade

    Upgrade maven/org.apache.kafka:kafka_2.12 to a version that resolves this vulnerability.

    Fixed in 2.8.1
  8. Upgrade

    Upgrade maven/org.apache.kafka:kafka_2.12 to a version that resolves this vulnerability.

    Fixed in 2.7.2
  9. Upgrade

    Upgrade maven/org.apache.kafka:kafka_2.12 to a version that resolves this vulnerability.

    Fixed in 2.6.3
  10. Upgrade

    Upgrade redhat/kafka-2.8.1 kafka-clients to a version that resolves this vulnerability.

    Fixed in 2.8.1
  11. Upgrade

    Upgrade Apache Kafka to a version that resolves this vulnerability.

    Fixed in 2.8.1
  12. Upgrade

    Upgrade Apache Kafka to a version that resolves this vulnerability.

    Fixed in 3.0.0

Event History

Sep 21, 2021
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 22, 2021
CVE Published
via MITRE·09:05 AM
Data Sourced
via MITRE·09:05 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 23, 2021
Advisory Published
11:18 PM
Sep 29, 2021
Data Sourced
via Red Hat·06:37 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2021-38153?

The severity of CVE-2021-38153 is medium.

2

Which components in Apache Kafka are vulnerable to CVE-2021-38153?

Some components in Apache Kafka are vulnerable to CVE-2021-38153.

3

How can I fix CVE-2021-38153?

To fix CVE-2021-38153, users should upgrade to Apache Kafka 2.8.1 or higher, or 3.0.0 or higher.

4

Where can I find more information about CVE-2021-38153?

You can find more information about CVE-2021-38153 at the following references: [link1](https://www.cve.org/CVERecord?id=CVE-2021-38153), [link2](https://nvd.nist.gov/vuln/detail/CVE-2021-38153), [link3](https://bugzilla.redhat.com/show_bug.cgi?id=2009041), [link4](https://access.redhat.com/errata/RHSA-2022:0219).

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203