Skip to content

Use of Uninitialized Variable in trilogy

Moderate severity GitHub Reviewed Published Jun 6, 2022 in trilogy-libraries/trilogy • Updated May 4, 2023

Package

bundler trilogy (RubyGems)

Affected versions

< 2.1.1

Patched versions

2.1.1

Description

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

@jhawthorn jhawthorn published to trilogy-libraries/trilogy Jun 6, 2022
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

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.133%
(50th percentile)

Weaknesses

CVE ID

CVE-2022-31026

GHSA ID

GHSA-5g4r-2qhx-vqfm

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.