CVE-2022-2469 json
GNU SASL libgsasl server-side read-out-of-bounds with malicious authenticated GSS-API client
published 4y ago modified 4mo ago also EUVD-2022-34729
- cvss
- 3.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
GNU SASL libgsasl server-side read-out-of-bounds with malicious authenticated GSS-API client
Patch / fix
- gnu gnu_sasl 2.0.1
- gsasl Debian 14, Debian 13, Debian 12 2.0.1-1
debian advisories DEBIAN-CVE-2022-2469
- gsasl Ubuntu Pro 14.04 LTS 1.8.0-2ubuntu2+esm1
- gsasl Ubuntu Pro 16.04 LTS 1.8.0-8ubuntu2+esm1
- gsasl Ubuntu Pro 18.04 LTS 1.8.0-8ubuntu3+esm2
- gsasl Ubuntu Pro 20.04 LTS 1.8.1-1ubuntu0.1~esm1
- gsasl Ubuntu Pro 22.04 LTS 1.10.0-5ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2022-2469
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- libgsasl Manager Server Module 4.3, Manager Proxy Module 4.3 1.8.0-150400.3.3.1
- libgsasl Manager Server Module 4.1, Manager Proxy Module 4.1 1.8.0-150200.3.3.1
- libgsasl Manager Server Module 4.2, Manager Proxy Module 4.2 1.8.0-150300.3.3.1
suse advisories SUSE-SU-2022:3563-1SUSE-SU-2022:3562-1SUSE-SU-2022:3561-1
Is CVE-2022-2469 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-2469 updated cvss 7.1
libgsasl: Out of bounds read causes DoS
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- GNU GNU SASL
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
gitlab.com
/gsasl/gsasl/-/commit/796e4197f696261c1f872d7576371232330bcc30
patch, third-party-advisory
-
debian.org
/security/2022/dsa-5189
vendor-advisory, third-party-advisory
-
gitlab.com
/gitlab-org/cves/-/blob/master/2022/CVE-2022-2469.json
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-2469
- NVD CVE-2022-2469
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.