# CVE-2017-5084: Information disclosure in Google Chrome prior to 59.0.3071.92

> A local attacker can read local files on Chrome OS by exploiting an inappropriate implementation in the image-burner service via D-Bus commands.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h662-qc36-6h52, UBUNTU-CVE-2017-5084

## What is CVE-2017-5084?

CVE-2017-5084 is a low-severity vulnerability in Google Chrome Os, published on 27 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Inappropriate implementation in image-burner in Google Chrome OS prior to 59.0.3071.92 allowed a local attacker to read local files via dbus-send commands to a BurnImage D-Bus endpoint.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-5084?

It affects 1 product.


Products: Google Chrome Os.

## How do I fix CVE-2017-5084?

Upgrade to a fixed version.

## Is CVE-2017-5084 being exploited?

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

## Other vulnerabilities in Google Chrome Os

- [CVE-2014-1708](https://insights.sbomify.com/CVE-2014-1708/): Code injection in n/a (critical 10.0)
- [CVE-2013-2833](https://insights.sbomify.com/CVE-2013-2833/): Use after free in n/a (critical 10.0)
- [CVE-2013-0915](https://insights.sbomify.com/CVE-2013-0915/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2864](https://insights.sbomify.com/CVE-2012-2864/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4050](https://insights.sbomify.com/CVE-2012-4050/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5084 and fix it if it is affected.

What it is: CVE-2017-5084 is a low-severity vulnerability in Google Chrome Os, published on 27 Oct 2017. 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-2017-5084 in the wild and no public exploit code.

Affected product: Google Chrome Os. 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-2017-5084/ (Markdown: https://insights.sbomify.com/CVE-2017-5084/index.md)
```

## Sources

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

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