# CVE-2018-17956: Password exposed in process listing

> Local attackers can read Samba share passwords from the process list due to insecure command-line argument handling in the YaST provisioning tool.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6xxx-c2gc-j39m, SUSE-SU-2022:3199-1, openSUSE-SU-2024:11535-1

## What is CVE-2018-17956?

CVE-2018-17956 is a low-severity vulnerability in SUSE yast2-samba-provision, published on 15 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In yast2-samba-provision up to and including version 1.0.1 the password for samba shares was provided on the command line to tools used by yast2-samba-provision, allowing local attackers to read them in the process list

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-17956?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-samba-provision` | SUSE:Linux Enterprise Module for Server Applications 15 SP4 | All versions | 1.0.5-150400.9.3.3 |
| `yast2-samba-provision` | openSUSE:Leap 15.4 | All versions | 1.0.5-150400.9.3.3 |
| `yast2-samba-provision` | openSUSE:Tumbleweed | All versions | 1.0.5-1.2 |

Products: Opensuse Yast2-Samba-Provision.

## How do I fix CVE-2018-17956?

Apply the vendor's patch.

## Is CVE-2018-17956 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17956 and fix it if it is affected.

What it is: CVE-2018-17956 is a low-severity vulnerability in SUSE yast2-samba-provision, published on 15 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17956 in the wild and no public exploit code.

Affected product: SUSE yast2-samba-provision. 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-2018-17956/ (Markdown: https://insights.sbomify.com/CVE-2018-17956/index.md)
```

## Sources

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

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