WaratekVRT Sign in

CVE-2023-31007 Apache Pulsar

Affected softwareApache Pulsar
Severity6.5 Medium CVSS 3.1 2 scores
Fixed in2.10.4, 2.11.1
WeaknessImproper authentication (CWE-287)
Published12 Jul 2023
Updated17 Jun 2026

Description

Improper Authentication vulnerability in Apache Software Foundation Apache Pulsar Broker allows a client to stay connected to a broker after authentication data expires if the client connected through the Pulsar Proxy when the broker is configured with authenticateOriginalAuthData=false or if a client connects directly to a broker with a specially crafted connect command when the broker is configured with authenticateOriginalAuthData=false. This issue affects Apache Pulsar: through 2.9.4, from 2.10.0 through 2.10.3, 2.11.0. 2.9 Pulsar Broker users should upgrade to at least 2.9.5. 2.10 Pulsar Broker users should upgrade to at least 2.10.4. 2.11 Pulsar Broker users should upgrade to at least 2.11.1. 3.0 Pulsar Broker users are unaffected. Any users running the Pulsar Broker for 2.8.* and earlier should upgrade to one of the above patched versions.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 3 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 1.0% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.

CVSS

6.5 MEDIUM v3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 6.5 MEDIUM CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N NVD Primary published
CVSS 3.1 0.0 NONE CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N security@apache.org Secondary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.apache.pulsar:pulsar-broker 2.9.0 2.10.4 unbounded
org.apache.pulsar:pulsar-broker 2.11.0 2.11.1 unbounded

Products and versions

2 products, 7 version entries
SourceVendorProductSchemeAffected versions
nvd apache pulsar generic < 2.9.5 · ≥ 2.10.0 and ≤ 2.10.3 · 2.11.0 · 2.11.0:candidate_1 · 2.11.0:candidate_5
osv org.apache.pulsar pulsar-broker generic ≥ 2.9.0 and < 2.10.4 · ≥ 2.11.0 and < 2.11.1

References

URLTags
https://github.com/apache/pulsar PACKAGE
https://lists.apache.org/thread/qxn99xxyp0zv6jchjggn3soyo5gvqfxj WEB

Timeline

Published2023-07-12By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.