Deserialization of Untrusted Data Affecting pki-symkey package, versions <0:10.8.3-1.module+el8.2.0+5925+bad5981a


Severity

Recommended
medium

Based on CentOS security rating.

Threat Intelligence

EPSS
0.6% (79th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS8-PKISYMKEY-2034369
  • published26 Jul 2021
  • disclosed27 Sept 2019

Introduced: 27 Sep 2019

CVE-2019-16942  (opens in a new tab)
CWE-502  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Centos:8 pki-symkey to version 0:10.8.3-1.module+el8.2.0+5925+bad5981a or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream pki-symkey package and not the pki-symkey package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the commons-dbcp (1.4) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of org.apache.commons.dbcp.datasources.SharedPoolDataSource and org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.

References

CVSS Scores

version 3.1