Skip to content

mellium.im/sasl authentication failure due to insufficient nonce randomness

Critical severity GitHub Reviewed Published Dec 31, 2022 to the GitHub Advisory Database • Updated May 20, 2024

Package

gomod mellium.im/sasl (Go)

Affected versions

< 0.3.1

Patched versions

0.3.1

Description

An issue was discovered in Mellium mellium.im/sasl before 0.3.1. When performing SCRAM-based SASL authentication, if the remote end advertises support for channel binding, no random nonce is generated (instead, the nonce is empty). This causes authentication to fail in the best case, but (if paired with a remote end that does not validate the length of the nonce) could lead to insufficient randomness being used during authentication.

References

Published by the National Vulnerability Database Dec 31, 2022
Published to the GitHub Advisory Database Dec 31, 2022
Reviewed Jan 4, 2023
Last updated May 20, 2024

Severity

Critical

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
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:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.201%
(58th percentile)

Weaknesses

CVE ID

CVE-2022-48195

GHSA ID

GHSA-gvfj-fxx3-j323

Source code

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