CVE-2022-3217: When logging in to a VBASE runtime project via Web-Remote, the product uses XOR with a static initial key to o

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2022-3217 is a high-severity flaw (CVSS 7.5) affecting vbase. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

When logging in to a VBASE runtime project via Web-Remote, the product uses XOR with a static initial key to obfuscate login messages. An unauthenticated remote attacker with the ability to capture a login session can obtain the login credentials.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Published	2022-09-16
Last modified	2026-06-17

Publisher (CNA): Tenable Network Security, Inc. · Vendor: visam

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

Am I affected?

Timeline

2022-09-16 22:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

visam vbase DOWNGRADE

Affected: 11.7.0.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 11.7.0.2

1. Check installed version

apt-cache policy vbase || rpm -q vbase || vbase --version

2. No fixed release: DOWNGRADE to a release before 11.7.0.2 (Debian / Ubuntu)

apt-cache madison vbase sudo apt install vbase=<VERSION_BEFORE_11.7.0.2> sudo apt-mark hold vbase

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vbase sudo dnf downgrade vbase-<VERSION_BEFORE_11.7.0.2> sudo dnf versionlock add vbase

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2022-3217?

vbase: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-3217 being exploited?

CVE-2022-3217 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-2022-3217 affect?

CVE-2022-3217 affects vbase. Severity is high (CVSS 7.5). When logging in to a VBASE runtime project via Web-Remote, the product uses XOR with a static initial key to obfuscate login messages. An unauthenticated remote attacker with the ability to capture a login session can obtain the login crede

How urgent is CVE-2022-3217?

Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-45876 MEDIUM 5.5 UPGRADE Versions of VISAM VBASE Automation Base prior to 11.7.5 may disclose information if a valid user opens a speci

References

← Back to latest CVEs