CVE-2022-3217
First published: Fri Sep 16 2022(Updated: )
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.
Credit: vulnreport@tenable.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| VISAM VBASE Pro-RT/ Server-RT (Web Remote) | =11.7.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-3217?
CVE-2022-3217 is considered a high severity vulnerability due to its potential for credential theft.
How do I fix CVE-2022-3217?
To mitigate CVE-2022-3217, ensure to implement a more secure authentication method that does not rely on static keys.
Who is affected by CVE-2022-3217?
CVE-2022-3217 affects users of VBASE version 11.7.0.2.
What kind of attack is possible with CVE-2022-3217?
CVE-2022-3217 allows an unauthenticated remote attacker to capture and decipher login credentials.
What products are involved in CVE-2022-3217?
The vulnerability CVE-2022-3217 involves the VISAM VBASE application.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/last-modified-date
- agent/references
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/visam
- canonical/visam vbase pro-rt/ server-rt (web remote)
- version/visam vbase pro-rt/ server-rt (web remote)/11.7.0.2