# CVE-2022-29869: Information disclosure in n/a

> Verbose logging in cifs-utils may leak sensitive information from files containing equal signs that are not valid credential files.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-29869, AZL-9588, CLSA-2026-1778015406, DEBIAN-CVE-2022-29869, GHSA-pwjc-pm2q-cpg2, SUSE-SU-2022:2801-1, SUSE-SU-2022:2802-1, SUSE-SU-2022:3525-1, UBUNTU-CVE-2022-29869, openSUSE-SU-2022:2801-1

## What is CVE-2022-29869?

CVE-2022-29869 is a medium-severity vulnerability in Debian Debian Linux, published on 28 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cifs-utils through 6.14, with verbose logging, can cause an information leak when a file contains = (equal sign) characters but is not a valid credentials file.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cifs-utils` | SUSE:Linux Enterprise Micro 5.2 | All versions | 6.9-150100.5.18.1 |
| `cifs-utils` | SUSE:Linux Enterprise Micro 5.3 | All versions | 6.15-150400.3.9.1 |
| `cifs-utils` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 6.9-150100.5.18.1 |
| `cifs-utils` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 6.15-150400.3.9.1 |
| `cifs-utils` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 6.9-13.23.1 |
| `cifs-utils` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 6.9-13.23.1 |
| `cifs-utils` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 6.9-13.23.1 |
| `cifs-utils` | openSUSE:Leap 15.3 | All versions | 6.9-150100.5.18.1 |
| `cifs-utils` | openSUSE:Leap 15.4 | All versions | 6.15-150400.3.9.1 |
| `cifs-utils` | openSUSE:Leap Micro 5.2 | All versions | 6.9-150100.5.18.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Samba Cifs-Utils.

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

Apply the vendor's patch.

## Is CVE-2022-29869 being exploited?

There is no known exploitation of CVE-2022-29869 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-29869 and fix it if it is affected.

What it is: CVE-2022-29869 is a medium-severity vulnerability in Debian Debian Linux, published on 28 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29869 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-29869/ (Markdown: https://insights.sbomify.com/CVE-2022-29869/index.md)
```

## Sources

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

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