# CVE-2015-5663: Privilege escalation in n/a

> Local attackers can gain privileges by tricking users into executing a Trojan horse file with a name similar to a selected extensionless file.

- **Severity:** High 7.4 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vm3c-vj26-xwxp

## What is CVE-2015-5663?

CVE-2015-5663 is a high-severity vulnerability in n/a, published on 30 Dec 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The file-execution functionality in WinRAR before 5.30 beta 5 allows local users to gain privileges via a Trojan horse file with a name similar to an extensionless filename that was selected by the user.

Weakness: CWE-264

## Which versions are affected by CVE-2015-5663?

It affects 1 product.


Products: Rarlab Winrar.

## How do I fix CVE-2015-5663?

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

## Is CVE-2015-5663 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-6218](https://insights.sbomify.com/CVE-2025-6218/): RARLAB WinRAR Path Traversal (high 7.8, exploited in the wild)
- [CVE-2023-38831](https://insights.sbomify.com/CVE-2023-38831/): RARLAB WinRAR Code Execution (high 7.8, exploited in the wild)
- [CVE-2018-20250](https://insights.sbomify.com/CVE-2018-20250/): WinRAR Absolute Path Traversal (high 7.8, exploited in the wild)
- [CVE-2008-7144](https://insights.sbomify.com/CVE-2008-7144/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1254](https://insights.sbomify.com/CVE-2004-1254/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5663 and fix it if it is affected.

What it is: CVE-2015-5663 is a high-severity vulnerability in n/a, published on 30 Dec 2015. 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-2015-5663 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-2015-5663/ (Markdown: https://insights.sbomify.com/CVE-2015-5663/index.md)
```

## Sources

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

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