dbcve.org
PulsarApplication · Apache

CVE-2023-31007

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 2.9.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Pulsar Broker has an improper authentication vulnerability where clients can remain connected after authentication data expires. This occurs when authenticateOriginalAuthData=false is configured, either through the Pulsar Proxy or via a specially crafted connect command when connecting directly to the broker. The vulnerability allows authenticated sessions to persist beyond the validity of their credentials.

MitigationUpgrade Apache Pulsar Broker to version 2.9.5, 2.10.4, 2.11.1 or later. Additionally, review and audit the authenticateOriginalAuthData configuration setting and ensure it is set appropriately for the deployment model.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PulsarApplication
Affected:< 2.9.5>= 2.10.0, <= 2.10.3= 2.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache Pulsar broker version
    Run the pulsar-admin brokers version command or check the version file in the Pulsar installation directory (typically in the 'version' file or via pulsar version CLI)
    Affected if The installed version is < 2.9.5 OR >= 2.10.0 and <= 2.10.3 OR = 2.11.0
  2. Locate the broker configuration file
    Find the Pulsar broker configuration file (broker.conf, standalone.conf, or the conf file specified at startup). The file is typically in the conf/ directory of the Pulsar installation.
    Affected if The configuration file exists and is in use by the broker
  3. Check authenticateOriginalAuthData setting
    Inspect the broker configuration file for the entry 'authenticateOriginalAuthData'. Also check for environment variable PULSAR_AUTHENTICATEORIGINALAUTHDATA if environment variables are used.
    Affected if authenticateOriginalAuthData is explicitly set to 'false' (case-insensitive) in the configuration or environment variable
  4. Check proxy configuration if applicable
    If using Pulsar Proxy, locate and inspect the proxy configuration file (proxy.conf) for the authenticateOriginalAuthData setting
    Affected if The proxy configuration file has authenticateOriginalAuthData set to 'false' and connects to a vulnerable broker version

You are affected if you are running a vulnerable Pulsar version AND authenticateOriginalAuthData is set to false in either the broker or proxy configuration, as this allows authenticated sessions to persist beyond credential expiry.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.9.5 or later
Fixed in 2.9.5
Interim mitigation

Upgrade Apache Pulsar Broker to version 2.9.5, 2.10.4, 2.11.1 or later. Additionally, review and audit the authenticateOriginalAuthData configuration setting and ensure it is set appropriately for the deployment model.

Recommended fix High confidence

Upgrade to Pulsar 2.9.5+, 2.10.4+, 2.11.1+, or 3.0+ (3.0 is unaffected)

  1. Identify current Apache Pulsar Broker version using pulsar-admin or broker logs
  2. For Pulsar < 2.9.5: Plan upgrade to version 2.9.5 or later (2.10.4+, 2.11.1+, or 3.0+)
  3. For Pulsar 2.10.0-2.10.3: Plan upgrade to version 2.10.4 or later (2.11.1+, or 3.0+)
  4. For Pulsar 2.11.0: Plan upgrade to version 2.11.1 or later (or 3.0+)
  5. Test upgrade in non-production environment first
  6. Schedule maintenance window and back up broker configuration
  7. Stop Pulsar Broker services
  8. Upgrade Pulsar Broker packages or Docker images to target version
Caveat Upgrading across major version branches (e.g., 2.x to 3.x) may require compatibility testing; review Apache Pulsar upgrade guides for breaking changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pulsar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31007 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data