First published: Tue Jul 11 2023(Updated: )
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.
Credit: security@apache.org security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Pulsar | =2.11.0 | |
Apache Pulsar | =2.11.0-candidate_1 | |
Apache Pulsar | =2.11.0-candidate_5 | |
Apache Pulsar | >=2.10.0<=2.10.3 | |
Apache Pulsar | <2.9.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-31007 is an improper authentication vulnerability in Apache Pulsar Broker.
CVE-2023-31007 allows a client to stay connected to a broker after authentication data expires.
CVE-2023-31007 has a severity score of 6.5 (Medium).
To fix CVE-2023-31007, update your Apache Pulsar Broker to version 2.11.1 or 2.10.4.
You can find more information about CVE-2023-31007 on the NIST website, Apache mailing list, and GitHub advisory.