Is CVE-2015-7529 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2015-7529 being exploited in the wild.

How severe is CVE-2015-7529?

Low severity, with a CVSS score of 3.1, published 6 November 2017.

Which products and versions are affected?

sosreport (PyPI) ECOSYSTEM:introduced=3.0, ECOSYSTEM:introduced=3.0,fixed=3.3.

Is there a fix for CVE-2015-7529?

Yes. sosreport (PyPI): upgrade to 3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2015-7529 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2015-7529?

Check whether you run sosreport (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2015-7529: SoSReport predictable temporary file names

CVE-2015-7529 · Severity: low · CVSS 3.1 · Published 2017-11-06

SoSReport is a system diagnostic tool that collects configuration and log files into an archive for troubleshooting. The tool creates temporary files in /tmp with predictable names, allowing a local attacker to pre-create symlinks to those locations and redirect the archive to arbitrary files. This could expose sensitive system data or allow privilege escalation through symlink attacks.

Technologies: sosreport (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2015-7529 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2015-7529 being exploited in the wild.
How severe is CVE-2015-7529?: Low severity, with a CVSS score of 3.1, published 6 November 2017.
Which products and versions are affected?: sosreport (PyPI) ECOSYSTEM:introduced=3.0, ECOSYSTEM:introduced=3.0,fixed=3.3.
Is there a fix for CVE-2015-7529?: Yes. sosreport (PyPI): upgrade to 3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2015-7529 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2015-7529?: Check whether you run sosreport (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

sosreport (PyPI): upgrade to 3.3 or later
```
pip install "sosreport>=3.3"
```

Technical details

The vulnerability is a symlink attack (CWE-59) affecting SoSReport 3.0 through 3.2.x, which uses predictable temporary file names in /tmp (e.g., sosreport-$hostname-$date.tar) without checking for existing symlinks before creating the archive. A local attacker with minimal privileges can create symlinks pointing to sensitive files or directories, then trigger sosreport execution; the tool will follow the symlink and overwrite the target file with the archive contents or expose system information to the attacker's readable location. The attack requires local filesystem access and knowledge of the hostname and date, but these are easily predictable. The vulnerability was fixed in SoSReport 3.3 by using mkdtemp() or similar secure temporary directory creation mechanisms.

Affected products

SoSReport SoSReport 3.0 through 3.2.x

Identifiers

CVE-2015-7529
GHSA-3g56-2hh3-35ph
PYSEC-2017-73

Timeline

2015: disclosed: CVE-2015-7529 assigned
2016: patched: Fixed in SoSReport 3.3

References

https://github.com/sosreport/sos/issues/696

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.