DbVisualizer is written in Java and can thus be exposed to vulnerabilities related to the Java Virtual Machine and the Java ecosystem. Since DbVisualizer is a rich client that runs on a local computer (as opposed to a web-based client) using its own Java VM, attacks that target cloud services or network communication are not a problem in terms of the DbVisualizer application itself, but vulnerabilities in the JDBC drivers that DbVisualizer uses to communicate with the database server can be exposed; this must be verified with the driver vendor.
Below is a list of specific vulnerabilities that have raised concerns among DbVisualizer users, with an explanation of if and how DbVisualizer is exposed, and what the proper mitigation is.
Apache Commons Text
DbVisualizer uses "Apache Commons Text" but since no remote code execution or contact with remote servers is invoked, the vulnerability is not affecting DbVisualizer.
Recommended Action: None.
DbVisualizer does not use the Spring Framework and is hence not exposed.
Recommended action: None
Sqlite-jdbc addresses a remote code execution vulnerability via JDBC URL. If connecting to SQLite database with a malicious JDBC URL arbritary code can be executed. This issue impacting versions 22.214.171.124 through 126.96.36.199 and has been fixed in version 188.8.131.52.
Recommended action: If you are using SQLite, update to SQLite version 184.108.40.206 or later.
Go to Tools / Driver Manager...
Select the SQLite driver.
Right click the row in Driver artifacts with org.xerial:sqlite-jdbc and click Edit Driver Artifacts...
Select veresion 220.127.116.11 or any later version and click OK.