visam vulnerabilities
Recent CVEs affecting visam products. 8 tracked.
visam has 8 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 7. Most recent: 2023-04-26. Highest priority: CVE-2022-3217 (score 54/100).
- CVE-2022-46300 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
- CVE-2022-46286 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
- 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
- CVE-2022-45468 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
- CVE-2022-45121 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
- CVE-2022-43512 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
- CVE-2022-41696 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
- CVE-2022-3217 HIGH 7.5 DOWNGRADE When logging in to a VBASE runtime project via Web-Remote, the product uses XOR with a static initial key to o
FAQ
How do I fix visam vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is visam being exploited right now?
None of the tracked visam CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which visam CVE should I patch first?
CVE-2022-3217 currently ranks highest (54/100): When logging in to a VBASE runtime project via Web-Remote, the product uses XOR with a static initial key to o.