# CVE-2016-5746: Information disclosure in n/a

> Local attackers can read sensitive passphrases for encrypted storage devices from temporary files created by SUSE storage tools.

- **Severity:** Medium 5.1 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v7w5-2xfr-963c, SUSE-SU-2016:2189-1, SUSE-SU-2016:2353-1, SUSE-SU-2016:2355-1

## What is CVE-2016-5746?

CVE-2016-5746 is a medium-severity vulnerability in Opensuse Leap, published on 26 Sep 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

libstorage, libstorage-ng, and yast-storage improperly store passphrases for encrypted storage devices in a temporary file on disk, which might allow local users to obtain sensitive information by reading the file, as demonstrated by /tmp/libstorage-XXXXXX/pwdf.

## Which versions are affected by CVE-2016-5746?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libstorage` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 2.25.35.1-3.1 |
| `yast2-storage` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 2.17.161-5.1 |
| `libstorage` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 2.25.35.1-3.1 |
| `libstorage` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 2.25.16.1-3.1 |
| `yast2-storage` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 2.17.161-5.1 |
| `libstorage` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 2.25.16.1-3.1 |
| `libstorage` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 2.25.35.1-3.1 |
| `yast2-storage` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.17.161-5.1 |
| `libstorage` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 2.25.35.1-3.1 |

Products: Opensuse Leap, Opensuse Libstorage, Opensuse Libstorage-Ng, Yast Yast-Storage.

## How do I fix CVE-2016-5746?

Apply the vendor's patch.

## Is CVE-2016-5746 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2015-4902](https://insights.sbomify.com/CVE-2015-4902/): Oracle Java SE Integrity Check (medium 5.3, exploited in the wild)
- [CVE-2017-14804](https://insights.sbomify.com/CVE-2017-14804/): package builds could use directory traversal to write outside of target area (critical 9.9)
- [CVE-2019-20787](https://insights.sbomify.com/CVE-2019-20787/): Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size. (critical 9.8)
- [CVE-2019-8341](https://insights.sbomify.com/CVE-2019-8341/): Code injection in n/a (critical 9.8)
- [CVE-2019-6438](https://insights.sbomify.com/CVE-2019-6438/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5746 and fix it if it is affected.

What it is: CVE-2016-5746 is a medium-severity vulnerability in Opensuse Leap, published on 26 Sep 2016. 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-2016-5746 in the wild and no public exploit code.

Affected product: Opensuse Leap. 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-2016-5746/ (Markdown: https://insights.sbomify.com/CVE-2016-5746/index.md)
```

## Sources

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

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