CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Vmware

CVE-2020-5413
Vmware Spring Integration vulnerability

Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown "deserialization gadgets" when configuring Kryo in code.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Spring Integration, Banking Corporate Lending Process Management, Banking Credit Facilities Process Management, Banking Supply Chain Finance, Banking Virtual Account Management, Flexcube Private Banking, Retail Customer Management And Segmentation Foundation, Retail Merchandising System. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Vmware Spring Integration runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Vmware products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.