# CVE-2017-7496: Privilege escalation in fedora-arm-installer

> Local attackers can escalate privileges in Fedora ARM installer due to unchecked mount failures on unsafe temporary directories.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c5w8-cwh4-jh73

## What is CVE-2017-7496?

CVE-2017-7496 is a high-severity vulnerability in Red Hat, Inc. fedora-arm-installer, published on 26 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

fedora-arm-installer up to and including 1.99.16 is vulnerable to local privilege escalation due to lack of checking the error condition of mount operation failure on unsafely created temporary directories.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-391 (DEPRECATED: Unchecked Error Condition)

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

It affects 1 product.


Products: Fedoraproject Arm Installer.

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

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

## Is CVE-2017-7496 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7496 is a high-severity vulnerability in Red Hat, Inc. fedora-arm-installer, published on 26 Jun 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-7496 in the wild and no public exploit code.

Affected product: Red Hat, Inc. fedora-arm-installer. 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-7496/ (Markdown: https://insights.sbomify.com/CVE-2017-7496/index.md)
```

## Sources

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

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