CVE-2020-26207

DatabaseSchemaViewer before version 2.7.4.3 is vulnerable to arbitrary code execution if a user is tricked into opening a specially crafted .dbschema file. The patch was released in v2.7.4.3. As a workaround, ensure .dbschema files from untrusted sources are not opened.

Weakness

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Affected Software

Potential Mitigations

• Make fields transient to protect them from deserialization.
• An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/586.html

References

• https://github.com/martinjw/dbschemareader/commit/4c0ab7b1fd8c4e3140f9fd54d303f107a9c8d994
• https://github.com/martinjw/dbschemareader/releases/tag/2.7.4.3
• https://github.com/martinjw/dbschemareader/security/advisories/GHSA-rfjh-m356-mpqf
• https://github.com/martinjw/dbschemareader/commit/4c0ab7b1fd8c4e3140f9fd54d303f107a9c8d994
• https://github.com/martinjw/dbschemareader/releases/tag/2.7.4.3
• https://github.com/martinjw/dbschemareader/security/advisories/GHSA-rfjh-m356-mpqf