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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Apache Software Foundation | Apache Qpid Proton C | ≤ 0.40.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | qpid-proton | No fix yet | — |
| Debian 13 | qpid-proton | No fix yet | — |
| Debian 12 | qpid-proton | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | qpid-proton | No fix yet | — |
| Ubuntu 26.04 LTS | qpid-proton | No fix yet | — |
| Ubuntu 24.04 LTS | qpid-proton | No fix yet | — |
| Ubuntu 22.04 LTS | qpid-proton | No fix yet | — |
| Ubuntu 20.04 LTS | qpid-proton | No fix yet | — |
Show 2 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 18.04 LTS | qpid-proton | No fix yet | — |
| Ubuntu 16.04 LTS | qpid-proton | No fix yet | — |
Azure Linux
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Azure Linux 3 | qpid-proton | No fix yet | — |