Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Qpid Proton C, a messaging library implementing the AMQP protocol, is affected. An attacker can send regular AMQP frames disguised as SASL authentication frames, which may bypass authentication, though the actual impact depends on how the application handles the missing user name.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they claim to be SASL frames. This allows authentication bypass. However there will be no user name set so the effects depend on how the application deals with this condition - which otherwise means that authentication has not completed yet. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Apache Software Foundation Apache Qpid Proton C
through 0.40.0