# CVE-2018-10892: Missing authorization in docker

> Attackers can modify host hardware settings like Bluetooth or brightness by accessing unblocked /proc/acpi paths in default Docker configurations.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 6 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-10892, GHSA-hg92-xfw5-qgvm, RHBA-2018:2796, RHSA-2018:2482, UBUNTU-CVE-2018-10892

## What is CVE-2018-10892?

CVE-2018-10892 is a medium-severity missing authorization vulnerability in Opensuse Leap, published on 6 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. The flaw allows an attacker to modify host's hardware like enabling/disabling bluetooth or turning up/down keyboard brightness.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docker` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-client` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-common` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-debuginfo` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-logrotate` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-lvm-plugin` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-novolume-plugin` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-rhel-push-plugin` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `docker-v1.10-migrator` | Red Hat:rhel_extras_other:7 | All versions | 2:1.13.1-74.git6e3bb8e.el7 |
| `podman` | Red Hat:rhel_extras_other:7 | All versions | 0:0.9.2-5.git37a2afe.el7_5 |
| `podman-debuginfo` | Red Hat:rhel_extras_other:7 | All versions | 0:0.9.2-5.git37a2afe.el7_5 |

Products: Docker Docker, Mobyproject Moby, Opensuse Leap, Redhat Enterprise Linux, Redhat Enterprise Linux Server, Redhat Openstack.

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

Apply the vendor's patch.

## Is CVE-2018-10892 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2014-9357](https://insights.sbomify.com/CVE-2014-9357/): Arbitrary Code Execution (critical 10.0)
- [CVE-2020-14298](https://insights.sbomify.com/CVE-2020-14298/): Privilege escalation in Docker (high 8.8)
- [CVE-2020-14300](https://insights.sbomify.com/CVE-2020-14300/): Privilege escalation in Docker (high 8.8)
- [CVE-2018-15514](https://insights.sbomify.com/CVE-2018-15514/): Deserialization in n/a (high 8.8)
- [CVE-2014-9356](https://insights.sbomify.com/CVE-2014-9356/): Path Traversal in Docker (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10892 is a medium-severity missing authorization vulnerability in Opensuse Leap, published on 6 Jul 2018. 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-10892 in the wild and no public exploit code.

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

## Sources

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

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