# CVE-2015-3156: Openstack DBaaS (Trove) Improper Link Resolution Before File Access

> Local attackers can modify configuration files via symlink attacks on temporary files in OpenStack Trove, potentially compromising database services.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 11 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-3156, GHSA-98c8-36p9-gw66, PYSEC-2026-1053, SUSE-SU-2016:0739-1, UBUNTU-CVE-2015-3156

## What is CVE-2015-3156?

CVE-2015-3156 is a medium-severity path traversal vulnerability in n/a, published on 11 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The _write_config function in trove/guestagent/datastore/experimental/mongodb/service.py, reset_configuration function in trove/guestagent/datastore/experimental/postgresql/service/config.py, write_config function in trove/guestagent/datastore/experimental/redis/service.py, _write_mycnf function in trove/guestagent/datastore/mysql/service.py, InnoBackupEx::_run_prepare function in trove/guestagent/strategies/restore/mysql_impl.py, InnoBackupEx::cmd function in trove/guestagent/strategies/backup/mysql_impl.py, MySQLDump::cmd in trove/guestagent/strategies/backup/mysql_impl.py, InnoBackupExIncremental::cmd function in trove/guestagent/strategies/backup/mysql_impl.py, _get_actual_db_status function in trove/guestagent/datastore/experimental/cassandra/system.py and trove/guestagent/datastore/experimental/cassandra/service.py, and multiple class CbBackup methods in trove/guestagent/strategies/backup/experimental/couchbase_impl.py in Openstack DBaaS (aka Trove) as packaged in Openstack before 2015.1.0 (aka Kilo) allows local users to write to configuration files via a symlink attack on a temporary file.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2015-3156?

3 open source packages ship an affected version, including trove. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `trove` | PyPI | All versions | 4.0.0a0 |
| `trove` | PyPI | All versions | 4.0.0a0 |
| `trove` | PyPI | All versions | 4.0.0a0 |
| `openstack-trove` | SUSE:OpenStack Cloud 5 | All versions | 2014.2.4.juno-15.1 |
| `openstack-trove-doc` | SUSE:OpenStack Cloud 5 | All versions | 2014.2.4.juno-15.1 |

Products: Openstack Trove.

## How do I fix CVE-2015-3156?

Upgrade trove to 4.0.0a0 or later.

## Is CVE-2015-3156 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3156 and fix it if it is affected.

What it is: CVE-2015-3156 is a medium-severity path traversal vulnerability in n/a, published on 11 Aug 2017. 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-2015-3156 in the wild and no public exploit code.

Affected packages and fixed versions:
- trove (PyPI): affected all versions; fixed in 4.0.0a0
- trove (PyPI): affected all versions; fixed in 4.0.0a0
- trove (PyPI): affected all versions; fixed in 4.0.0a0

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-2015-3156/ (Markdown: https://insights.sbomify.com/CVE-2015-3156/index.md)
```

## Sources

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

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