# CVE-2022-2469: Memory corruption in GNU SASL

> A malicious authenticated GSS-API client can trigger an out-of-bounds read in the GNU SASL server, potentially causing a crash or information disclosure.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-2469, DSA-5189-1, GHSA-r9xr-xfwx-6crw, MGASA-2022-0298, OESA-2024-1351, OESA-2024-1441, OESA-2024-1442, OESA-2024-1443, OESA-2024-1444, OESA-2024-1445, SUSE-SU-2022:3561-1, SUSE-SU-2022:3562-1, SUSE-SU-2022:3563-1, UBUNTU-CVE-2022-2469, USN-6169-1, openSUSE-SU-2024:12325-1, openSUSE-SU-2024:13666-1

## What is CVE-2022-2469?

CVE-2022-2469 is a low-severity memory corruption vulnerability in Debian Debian Linux, published on 19 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

GNU SASL libgsasl server-side read-out-of-bounds with malicious authenticated GSS-API client

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-2469?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libgsasl` | SUSE:Manager Proxy Module 4.1 | All versions | 1.8.0-150200.3.3.1 |
| `libgsasl` | SUSE:Manager Proxy Module 4.2 | All versions | 1.8.0-150300.3.3.1 |
| `libgsasl` | SUSE:Manager Proxy Module 4.3 | All versions | 1.8.0-150400.3.3.1 |
| `libgsasl` | SUSE:Manager Server Module 4.1 | All versions | 1.8.0-150200.3.3.1 |
| `libgsasl` | SUSE:Manager Server Module 4.2 | All versions | 1.8.0-150300.3.3.1 |
| `libgsasl` | SUSE:Manager Server Module 4.3 | All versions | 1.8.0-150400.3.3.1 |

Products: Debian Debian Linux, Gnu Gnu Sasl.

## How do I fix CVE-2022-2469?

Apply the vendor's patch.

## Is CVE-2022-2469 being exploited?

There is no known exploitation of CVE-2022-2469 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2469 and fix it if it is affected.

What it is: CVE-2022-2469 is a low-severity memory corruption vulnerability in Debian Debian Linux, published on 19 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2469 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2469/ (Markdown: https://insights.sbomify.com/CVE-2022-2469/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2469
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2469
- OSV: https://osv.dev/vulnerability/CVE-2022-2469

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2469/
Summaries are generated and may contain mistakes; the official description above is the record.