-
Notifications
You must be signed in to change notification settings - Fork 769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Result of a code analysis #267
Comments
I am interested in pretty much all of them. The sloppy return errors code handling is something I have spotted too. I plan to enhance the code over time... One PR at a time. |
The error description is attached. If you have any questions, please ask For the sake of simplicity, I have attached all routines with errors. I have added the errors themselves as a comment with my initials DJ. I hope it is OK that the error description is written in German
|
Great. There is an error in Line 259 in MQTTFormat.c. |
In my research project, I analyzed the MQTT stack for buffer overflow errors. The analysis is based on a code review. In particular, it was checked whether all pointers point to a valid area. I found no errors regarding a buffer overflow, so attackers cannot use the protocol as a gateway into a system.
However, there are errors in the code, e.g.
Unfortunately, I don't have the time to correct these errors. However, if you are interested, I would be happy to send you a detailed description here.
The text was updated successfully, but these errors were encountered: