CVE-2013-3496: Infotecs ViPNet Client 3.2.10 (15632) and earlier, ViPNet Coordinator 3.2.10 (15632) and earlier, ViPNet Perso

Q: How do I fix CVE-2013-3496?

vipnet client: upgrade to newer than 3.2.10; vipnet coordinator: upgrade to newer than 3.2.10; vipnet personal firewall: upgrade to newer than 3.1. Exact commands for each OS are on this page.

Q: Is CVE-2013-3496 being exploited?

CVE-2013-3496 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-3496 affect?

CVE-2013-3496 affects vipnet client, vipnet coordinator, vipnet personal firewall. Severity is high (CVSS 7.2). 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 fol

Routine

HIGH 7.2UPGRADEUPGRADEUPGRADE

CVE-2013-3496 is a high-severity flaw (CVSS 7.2) affecting vipnet client, vipnet coordinator, vipnet personal firewall. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-264
Published	2013-05-22
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: infotecs

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2013-05-22 13:29 UTCPublished CVE record published
2026-06-16 23:55 UTCUpdated Record last modified

infotecs vipnet client UPGRADE

Affected: <= 3.2.10

Fixed in: newer than 3.2.10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vipnet-client || rpm -q vipnet-client || vipnet-client --version

2. UPGRADE to newer than 3.2.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vipnet-client

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vipnet-client

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

infotecs vipnet coordinator UPGRADE

Affected: <= 3.2.10

Fixed in: newer than 3.2.10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vipnet-coordinator || rpm -q vipnet-coordinator || vipnet-coordinator --version

2. UPGRADE to newer than 3.2.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vipnet-coordinator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vipnet-coordinator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

infotecs vipnet personal firewall UPGRADE

Affected: <= 3.1

Fixed in: newer than 3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vipnet-personal-firewall || rpm -q vipnet-personal-firewall || vipnet-personal-firewall --version

2. UPGRADE to newer than 3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vipnet-personal-firewall

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vipnet-personal-firewall

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

infotecs vipnet safedisk UPGRADE

Affected: <= 4.1

Fixed in: newer than 4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vipnet-safedisk || rpm -q vipnet-safedisk || vipnet-safedisk --version

2. UPGRADE to newer than 4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vipnet-safedisk

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vipnet-safedisk

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-3496?

vipnet client: upgrade to newer than 3.2.10; vipnet coordinator: upgrade to newer than 3.2.10; vipnet personal firewall: upgrade to newer than 3.1. Exact commands for each OS are on this page.

Is CVE-2013-3496 being exploited?

CVE-2013-3496 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-3496 affect?

CVE-2013-3496 affects vipnet client, vipnet coordinator, vipnet personal firewall. Severity is high (CVSS 7.2). 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 fol

How urgent is CVE-2013-3496?

Priority 33/100. High severity

Related CVEs

CVE-2017-9606 HIGH 7.3 UPGRADE UPGRADE Infotecs ViPNet Client and Coordinator before 4.3.2-42442 allow local users to gain privileges by placing a Tr

References

← Back to latest CVEs