rabbitmq-server: RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1, Atom exhaustion: OAuth2 JWT tag: scope values. extractscopes/1 parses scopes of the form .tag: and calls rabbitdatacoercion:toatom() to convert to a tag atom. The token signature is verified first, so the attacker cannot forge scopes , but in IdP configurations where scope content is user-influenced, each login with a novel tag value leaks one In deployments where users can influence the scopes included in their IdP-issued JWT rabbitmqauthbackendoauth2 enabled IdP permits attacker-influenced scope values in signed tokens. This issue is fixed in versions 3.13.15 and 4.0.22 and 4.1.11 and 4.2.6 and 4.3.1.
Text from CVE List
Affected versions 5
- rabbitmq-serveraffected: >= 3.13.0, < 3.13.15CVE List
- rabbitmq-serveraffected: >= 4.0.0, < 4.0.22CVE List
- rabbitmq-serveraffected: >= 4.1.0, < 4.1.11CVE List
- rabbitmq-serveraffected: >= 4.2.0, < 4.2.6CVE List
- rabbitmq-serveraffected: >= 4.3.0, < 4.3.1CVE List
References 5
- github.com/rabbitmq/rabbitmq-server/commit/9a44124d9c932d6fc7d2a3b945e5a143e547bcb6Fixvia CVE List
- github.com/rabbitmq/rabbitmq-server/commit/c5690583a53789a3bf00cca508b43e8246db0d11Fixvia CVE List
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6Fixvia CVE List
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1Fixvia CVE List
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-89p2-f5cv-x5cgAdvisoryvia CVE List