fix: remove unsafe exec() in mqtt.c#3
Merged
ErichStyger merged 1 commit intoMay 7, 2026
Merged
Conversation
Automated security fix generated by Orbis Security AI
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
2 participants
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.
Summary
Fix high severity security issue in
Firmware/PicoW_ClockMaster/src/mqtt.c.Vulnerability
V-004Firmware/PicoW_ClockMaster/src/mqtt.c:223Description: The MQTT client in PicoW_ClockMaster establishes broker connections for clock and motor control without evidence of TLS encryption or client authentication. Any attacker on the same network can connect to the MQTT broker, subscribe to control topics to observe commands, and publish spoofed motor position or LED commands that the PicoW will execute.
Changes
Firmware/PicoW_ClockMaster/src/mqtt.cVerification
Automated security fix by OrbisAI Security