# CVE-2013-3496: Privilege escalation in n/a

> Local attackers can escalate privileges by placing malicious files in a directory with weak permissions in Infotecs ViPNet products.

- **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:** 22 May 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2qhm-42jf-9593

## What is CVE-2013-3496?

CVE-2013-3496 is a high-severity vulnerability in n/a, published on 22 May 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Infotecs ViPNet Client 3.2.10 (15632) and earlier, ViPNet Coordinator 3.2.10 (15632) and earlier, ViPNet Personal Firewall 3.1 and earlier, and ViPNet SafeDisk 4.1 (0.5643) and earlier use weak permissions (Everyone: Full Control) for a folder under %PROGRAMFILES%\Infotecs, which allows local users to gain privileges via a Trojan horse (1) executable file or (2) DLL file.

Weakness: CWE-264

## Which versions are affected by CVE-2013-3496?

It affects 4 products.


Products: Infotecs Vipnet Client, Infotecs Vipnet Coordinator, Infotecs Vipnet Personal Firewall, Infotecs Vipnet Safedisk.

## How do I fix CVE-2013-3496?

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

## Is CVE-2013-3496 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9606](https://insights.sbomify.com/CVE-2017-9606/): Privilege escalation in n/a (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3496 and fix it if it is affected.

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

## Sources

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

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