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

> Local attackers can exploit SQLite's temporary file handling to read sensitive data or crash the application via the current working directory.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** DEBIAN-CVE-2016-6153, DLA-543-1, GHSA-c7vx-xpvf-fj57, MGASA-2016-0255, SUSE-SU-2016:1945-1, SUSE-SU-2016:2021-1, UBUNTU-CVE-2016-6153

## What is CVE-2016-6153?

CVE-2016-6153 is a medium-severity vulnerability in Fedoraproject Fedora, 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

os_unix.c in SQLite before 3.13.0 improperly implements the temporary directory search algorithm, which might allow local users to obtain sensitive information, cause a denial of service (application crash), or have unspecified other impact by leveraging use of the current working directory for temporary files.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sqlite3` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 3.8.10.2-3.1 |
| `sqlite3` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 3.7.6.3-1.4.6.1 |
| `sqlite3` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 3.8.10.2-3.1 |
| `sqlite3` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 3.7.6.3-1.4.6.1 |
| `sqlite3` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 3.8.10.2-3.1 |
| `sqlite3` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 3.7.6.3-1.4.6.1 |
| `sqlite3` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 3.8.10.2-3.1 |
| `sqlite3` | SUSE:Studio Onsite 1.3 | All versions | 3.7.6.3-1.4.6.1 |

Products: Fedoraproject Fedora, Opensuse Leap, Sqlite Sqlite.

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

Upgrade to a fixed version.

## Is CVE-2016-6153 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6153 is a medium-severity vulnerability in Fedoraproject Fedora, 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-6153 in the wild and no public exploit code.

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

## Sources

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

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