Repository navigation
mqtt-hivemq: re-check permissions when a rejected subscribe is retried - #262
Merged
Merged
Conversation
This was referenced Nov 7, 2026
Merged
alexrobin
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a permission bypass in the HiveMQ extension: a retried SUBSCRIBE was accepted without a permission check.
Closes #257. Part of #249.
Problem
OshExtension.subscribeToTopicrecorded the topic for the client before the handler checked permissions. When the check failed, the topic stayed recorded. The same SUBSCRIBE sent again found the topic, skipped the handler, and was accepted. The client then got every message on that topic, for example data that an allowed client had subscribed to. Two SUBSCRIBEs sent at the same time had the same gap.Fix
Testing
New
TestOshExtension(the module had no tests):On a test node with CS API access control on, an admin client subscribed to an observation topic and an anonymous client tried the same topic:
Independent of the consys-mqtt stack (#261). It merges cleanly with master and with #204, which also changes
OshExtension.java.