# CVE-2014-5507: Privilege escalation in n/a

> Local attackers can escalate privileges by replacing the service executable due to weak file permissions on iBackup.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 3 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r5jr-8rcw-p6vw

## What is CVE-2014-5507?

CVE-2014-5507 is a high-severity vulnerability in n/a, published on 3 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

iBackup 10.0.0.32 and earlier uses weak permissions (Everyone: Full Control) for ib_service.exe, which allows local users to gain privileges via a Trojan horse file.

Weakness: CWE-264

## Which versions are affected by CVE-2014-5507?

It affects 1 product.


Products: Pro Softnet Corporation Ibackup.

## How do I fix CVE-2014-5507?

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

## Is CVE-2014-5507 being exploited?

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

Public exploit code:

- iBackup 10.0.0.32 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5507 and fix it if it is affected.

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

## Sources

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

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