Authentication weakening via empty SCRAM nonce
Published Dec 31, 2022 · Updated Apr 11, 2025
Improper authentication in Mellium mellium.im/sasl before 0.3.1 allows remote attackers to weaken SCRAM authentication via an empty nonce. The SCRAM authentication path uses an empty nonce instead of generating a random value when the remote peer advertises channel binding. A server that validates nonce length rejects the exchange; exposure requires a peer that accepts the empty nonce, weakening authentication randomness.
Summary
What happened
Improper authentication in Mellium mellium.im/sasl before 0.3.1 allows remote attackers to weaken SCRAM authentication via an empty nonce. The SCRAM authentication path uses an empty nonce instead of generating a random value when the remote peer advertises channel binding. A server that validates nonce length rejects the exchange; exposure requires a peer that accepts the empty nonce, weakening authentication randomness.
The record
- CVE
- CVE-2022-48195
- Published
- Dec 31, 2022
- Updated
- Apr 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo