dbcve.org
SaslApplication · Mellium

CVE-2022-48195

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Mellium SASL library (mellium.im/sasl) before version 0.3.1 contains a flaw in SCRAM-based authentication where a random nonce is not generated when the remote server advertises support for channel binding—instead the nonce remains empty. This causes authentication failures or, more seriously, could lead to insufficient randomness in the authentication mechanism if the server does not validate nonce length.

MitigationUpgrade the mellium.im/sasl library to version 0.3.1 or later, which implements proper random nonce generation. Then thoroughly test SASL authentication flows to confirm functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SaslApplication
Affected:= 0.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed mellium.im/sasl version
    Review your project's go.mod file for the mellium.im/sasl version entry, or run 'go list -m mellium.im/sasl' in your project directory to get the exact version
    Affected if The version listed is exactly 0.3.0
  2. Confirm SCRAM authentication is in use
    Search your codebase for imports of mellium.im/sasl and verify that SCRAM-based authentication mechanisms (SCRAM-SHA-1, SCRAM-SHA-256, or similar) are configured or used in your authentication flow
    Affected if Your application uses SCRAM-based SASL authentication with the mellium library
  3. Check if your server supports channel binding
    Examine your SASL server configuration or logs to determine whether the remote server advertises support for channel binding (TLS-unique or TLS-exporter mechanisms)
    Affected if The server you authenticate against advertises channel binding support while using mellium.im/sasl version 0.3.0
  4. Review authentication logs for failures
    Search authentication and application logs for errors related to nonce validation, authentication failures, or SCRAM handshake errors that occurred during SASL authentication attempts
    Affected if You observe authentication failures or nonce-related errors in logs when authenticating against a channel-binding-capable server

You are affected if mellium.im/sasl version 0.3.0 is installed and your SASL authentication flow interacts with a server that supports channel binding, potentially causing authentication failures or weak nonce generation

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the mellium.im/sasl library to version 0.3.1 or later, which implements proper random nonce generation. Then thoroughly test SASL authentication flows to confirm functionality.

Recommended fix High confidence

0.3.1 or later

  1. Upgrade the mellium.im/sasl package to version 0.3.1 or later
  2. Verify the upgrade by checking the installed package version (e.g., using `go list -m mellium.im/sasl` or checking go.mod)
  3. Run tests to confirm SCRAM-based authentication now generates proper random nonces

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sasl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-48195 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data