Use of Uninitialized Variable in trilogy
Moderate severity
GitHub Reviewed
Published
Jun 6, 2022
in
trilogy-libraries/trilogy
•
Updated May 4, 2023
Description
Published to the GitHub Advisory Database
Jun 6, 2022
Reviewed
Jun 6, 2022
Published by the National Vulnerability Database
Jun 9, 2022
Last updated
May 4, 2023
Impact
When authenticating, a malicious server could return a specially crafted authentication packet, causing the client to read and return up to 12 bytes of data from an uninitialized variable in stack memory.
Patches
Users of the trilogy gem should upgrade to version 2.1.1
Workarounds
This issue can be avoided by only connecting to trusted servers.
Acknowledgements
We would like to thank Sergei Volokitin for reporting this vulnerability
For more information
If you have any questions or comments about this advisory:
References