# CVE-2016-5847: Privilege escalation in n/a

> Local attackers can gain privileges by exploiting a hard link attack to modify permissions of files extracted by the SAPCAR utility.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/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:** No
- **Published:** 12 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3gxr-2xmf-3h63

## What is CVE-2016-5847?

CVE-2016-5847 is a medium-severity vulnerability in n/a, published on 12 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SAP SAPCAR allows local users to change the permissions of arbitrary files and consequently gain privileges via a hard link attack on files extracted from an archive, possibly related to SAP Security Note 2327384.

Weakness: CWE-264

## Which versions are affected by CVE-2016-5847?

It affects 1 product.


Products: Sap Sapcar Archive Tool.

## How do I fix CVE-2016-5847?

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

## Is CVE-2016-5847 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-5847 exists.

Public exploit code:

- SAP SAPCAR - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5847 and fix it if it is affected.

What it is: CVE-2016-5847 is a medium-severity vulnerability in n/a, published on 12 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-5847 exists.

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-2016-5847/ (Markdown: https://insights.sbomify.com/CVE-2016-5847/index.md)
```

## Sources

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

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