# CVE-2018-16264: Information disclosure in n/a

> An unprivileged process can acquire sensitive information or partially control Bluetooth due to improper D-Bus security policy configurations in Tizen.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/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:** No
- **Published:** 22 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gcr3-7gvg-jhhf

## What is CVE-2018-16264?

CVE-2018-16264 is a medium-severity vulnerability in n/a, published on 22 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The BlueZ system service in Tizen allows an unprivileged process to partially control Bluetooth or acquire sensitive information, due to improper D-Bus security policy configurations. This affects Tizen before 5.0 M1, and Tizen-based firmwares including Samsung Galaxy Gear series before build RE2.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Linux Tizen.

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

No fix has been published for CVE-2018-16264 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-16264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-25434](https://insights.sbomify.com/CVE-2021-25434/): Code injection in Tizen wearable devices (critical 9.8)
- [CVE-2021-25435](https://insights.sbomify.com/CVE-2021-25435/): Code injection in Tizen wearable devices (critical 9.8)
- [CVE-2021-25436](https://insights.sbomify.com/CVE-2021-25436/): Code injection in Tizen wearable devices (critical 9.8)
- [CVE-2021-25437](https://insights.sbomify.com/CVE-2021-25437/): Missing authorization in Tizen wearable devices (critical 9.8)
- [CVE-2018-16262](https://insights.sbomify.com/CVE-2018-16262/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16264 is a medium-severity vulnerability in n/a, published on 22 Jan 2020. 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-2018-16264 in the wild and no public exploit code.

Affected product: n/a. 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-16264/ (Markdown: https://insights.sbomify.com/CVE-2018-16264/index.md)
```

## Sources

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

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