CVE-2018-16263 The PulseAudio system service in Tizen allows an unprivileged process to control its A2DP MediaEndpoint, due to improper D-Bus security policy configurations.
High 8.8
Published
Updated
Check this codebase for CVE-2018-16263 and fix it if it is affected.
What it is: CVE-2018-16263 is a high-severity vulnerability in n/a, published on 22 Jan 2020.
Exploitation: There is no known exploitation of CVE-2018-16263 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-16263/ (Markdown: https://insights.sbomify.com/CVE-2018-16263/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2018-16263?
CVE-2018-16263 is a high-severity vulnerability in n/a, published on 22 Jan 2020.
Official description
The PulseAudio system service in Tizen allows an unprivileged process to control its A2DP MediaEndpoint, 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-269
Which versions are affected by CVE-2018-16263?
It affects 1 product.
Products include Linux Tizen.
How do I fix CVE-2018-16263?
No fix has been published for CVE-2018-16263 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-16263 being exploited?
There is no known exploitation of CVE-2018-16263 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-5h96-c4j5-cc68.