VRT
391,192 CVEs tracked ·
15,442 in RASP scope ·
data as of 20 hours ago
VRT
391,192 CVEs tracked ·
15,442 in RASP scope ·
data as of 20 hours ago
CVE-2024-27309While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not be correctly enforced. Two preconditions are needed to trigger the bug: 1. The administrator decides to remove an ACL 2. The resource associated with the removed ACL continues to have two or more other ACLs associated with it after the removal. When those two preconditions are met, Kafka will treat the resource as if it had only one ACL associated with it after the removal, rather than the two or more that would be correct. The incorrect condition is cleared by removing all brokers in ZK mode, or by adding a new ACL to the affected resource. Once the migration is completed, there is no metadata loss (the ACLs all remain). The full impact depends on the ACLs in use. If only ALLOW ACLs were configured during the migration, the impact would be limited to availability impact. if DENY ACLs were configured, the impact could include confidentiality and integrity impact depending on the ACLs configured, as the DENY ACLs might be ignored due to this vulnerability during the migration period.
CWE-863 · Incorrect authorization
No public exploit
Nothing published shows this CVE being exploited, which is not the same as ruling it out. nothing published in 2 years.
CVSS E:U
In RASP's scope with an upstream fix path, but nobody has published a working exploit. That is a statement about what has been published, not a finding that the defect is unreachable or unimportant.
| Decided by | no-exploit-published : A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all |
|---|---|
| Finding | This CVE is not listed in CISA KEV, CISA Vulnrichment records no active exploitation, and no reviewed exploit catalogue carries an entry for it. Nobody has published something a stranger can run, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious. |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
1 metric
VRT selects the newest version's highest entry and
publishes it as cvssScore, newest rather than largest because scores are not comparable
across versions, and highest rather than first because the first entry is frequently a CNA placeholder
scoring 0.0 over NVD's own analysis.
| Version | Score | Band | Vector | Assigner | Type | |
|---|---|---|---|---|---|---|
| CVSS 3.1 | 7.4 | HIGH | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
CISA-ADP | Secondary | published |
| Advisory | Type | Quarter | Products Oracle named in risk matrix |
|---|---|---|---|
| Oracle Critical Patch Update July 2025 ↗ | CPU | 2025-Q3 | Oracle Siebel CRM / Event Publish and Subscribe (Apache Kafka) (25.0-25.5) |
| Oracle Critical Patch Update January 2025 ↗ | CPU | 2025-Q1 | Oracle Communications Applications / Solution Designer (Apache Kafka) (8.0.0.3, 8.1.0.1) |
| Family | Component | Oracle's version cell (verbatim) | Indexed as |
|---|---|---|---|
| Oracle Communications Applications | Solution Designer (Apache Kafka) | 8.0.0.3, 8.1.0.1 | 8.0.0.3 · 8.1.0.1 |
| Oracle Siebel CRM | Event Publish and Subscribe (Apache Kafka) | 25.0-25.5 |
| Package Coordinate | Introduced | Fixed | Last affected |
|---|---|---|---|
org.apache.kafka:kafka-metadata |
3.5.0 | 3.6.2 |
unbounded |
| Source | Vendor | Product | Scheme | Affected Versions |
|---|---|---|---|---|
| nvd | apache | kafka | generic | ≥ 3.5.0 and ≤ 3.6.1 |
| osv | org.apache.kafka | kafka-metadata | generic | ≥ 3.5.0 and ＜ 3.6.2 |
| Published | 2024-04-12 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-06-17 | NVD's own last-modified date for this record. |