# CVE-2018-14650: Information disclosure in sos-collector

> Local attackers can read sensitive data collected by sos-collector due to insecure default file permissions in the /var/tmp directory.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4pjf-x44m-95hq, RHSA-2018:3663

## What is CVE-2018-14650?

CVE-2018-14650 is a medium-severity vulnerability in Redhat Enterprise Linux Desktop, published on 27 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

It was discovered that sos-collector does not properly set the default permissions of newly created files, making all files created by the tool readable by any local user. A local attacker may use this flaw by waiting for a legit user to run sos-collector and steal the collected data in the /var/tmp directory.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sos-collector` | Red Hat:enterprise_linux:7::client | All versions | 0:1.5-3.el7_6 |
| `sos-collector` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.5-3.el7_6 |
| `sos-collector` | Red Hat:enterprise_linux:7::server | All versions | 0:1.5-3.el7_6 |
| `sos-collector` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.5-3.el7_6 |

Products: Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation, Sos-Collector Project Sos-Collector.

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

Apply the vendor's patch.

## Is CVE-2018-14650 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux Desktop

- [CVE-2016-5405](https://insights.sbomify.com/CVE-2016-5405/): Information disclosure in n/a (critical 9.8)
- [CVE-2016-7050](https://insights.sbomify.com/CVE-2016-7050/): Deserialization in n/a (critical 9.8)
- [CVE-2014-8241](https://insights.sbomify.com/CVE-2014-8241/): Null dereference in n/a (critical 9.8)
- [CVE-2014-8567](https://insights.sbomify.com/CVE-2014-8567/): Denial of service in n/a (critical 9.4)
- [CVE-2018-10897](https://insights.sbomify.com/CVE-2018-10897/): Path traversal in yum-utils: (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14650 is a medium-severity vulnerability in Redhat Enterprise Linux Desktop, published on 27 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-14650 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux Desktop. 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-14650/ (Markdown: https://insights.sbomify.com/CVE-2018-14650/index.md)
```

## Sources

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

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