CVE-2020-26945

MyBatis before 3.5.6 mishandles deserialization of object streams.

MyBatis before 3.5.6 mishandles deserialization of object streams.

MyBatis before 3.5.6 mishandles deserialization of object streams.

MyBatis before 3.5.6 mishandles deserialization of object streams leading to potential cache poisoning.

MyBatis before 3.5.6 mishandles deserialization of object streams leading to potential cache poisoning.

The MyBatis data mapper framework makes it easier to use a relational database with object-oriented applications. MyBatis couples objects with stored procedures or SQL statements using a XML descriptor or annotations. Simplicity is the biggest advantage of the MyBatis data mapper over object relational mapping tools. To use the MyBatis data mapper, you rely on your own objects, XML, and SQL. There is little to learn that you don't already know. With the MyBatis data mapper, you have the full power of both SQL and stored procedures at your fingertips. The MyBatis project is developed and maintained by a team that includes the original creators of the "iBATIS" data mapper. The Apache project was retired and continued here.

Security Fix(es):

MyBatis before 3.5.6 mishandles deserialization of object streams.(CVE-2020-26945)

TuxCare rebuilt org.mybatis:mybatis to address 1 CVE. Fixed in 2.3.5-tuxcare.1.

These are all security issues fixed in the mybatis-3.5.6-1.6 package on the GA media of openSUSE Tumbleweed.