Mellium Sasl 0.3.0
Approved changes feed: RSS · Atom
cpe:2.3:a:mellium:sasl:0.3.0:*:*:*:*:*:*:*
part: a version: 0.3.0 update: *
| Vendor | Mellium (52ca4884-39b9-510f-bb76-829694058ccb) |
|---|---|
| Product | Sasl (4715e9ad-acd8-5a37-be56-ffd8388db9ad) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/mellium/sasl |
purl2cpe | 2026-06-01 10:16:10.821658 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-48195 |
vulnerable | 2026-06-08 05:50:41.595616 |
Details available
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.
Published: 2022-12-31T00:00:00.000Z
Updated: 2025-04-11T14:46:45.333Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.