Advisory record · GHSA-c57v-4vg5-cm2x

Apache Pulsar SASL Authentication Provider observable timing discrepancy vulnerability

CVSS 7.4 HighEPSS 0.0076 · 55th percentile

Published by the GitHub Advisory Database at 7 Feb 2024, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.pulsar:pulsar-broker-auth-saslMaven<2.11.3 || >=3.0.0, <3.0.2 || >=3.1.0, <3.1.12.11.3, 3.0.2, 3.1.1
Identifiers
GHSA-c57v-4vg5-cm2x · CVE-2023-51437
Weakness (CWE)
CWE-200 · CWE-203
Published
7 Feb 2024
Updated
22 Jul 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Pulsar's pulsar-broker-auth-sasl package is affected in versions below 2.11.3, from 3.0.0 up to but not including 3.0.2, and from 3.1.0 up to but not including 3.1.1. A timing discrepancy in signature verification can let an attacker forge a SASL Role Token that passes verification; the source does not describe the required network access. Upgrade to 2.11.3, 3.0.2, or 3.1.1, and consider rotating the secret in the saslJaasServerRoleTokenSignerSecretPath file.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (apache)
  • CISA KEV Not listed.
  • EPSS 0.0076, the 55th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.