Cryptographic Issues Affecting java-1.5.0-ibm-javacomm package, versions <1:1.5.0.16.2-1jpp.1.el6_4


Severity

Recommended
high

Based on CentOS security rating.

Threat Intelligence

EPSS
1.22% (86th 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 Cryptographic Issues vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS6-JAVA150IBMJAVACOMM-2079879
  • published26 Jul 2021
  • disclosed4 Feb 2013

Introduced: 4 Feb 2013

CVE-2013-0169  (opens in a new tab)
CWE-310  (opens in a new tab)

How to fix?

Upgrade Centos:6 java-1.5.0-ibm-javacomm to version 1:1.5.0.16.2-1jpp.1.el6_4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream java-1.5.0-ibm-javacomm package and not the java-1.5.0-ibm-javacomm package as distributed by Centos. See How to fix? for Centos:6 relevant fixed versions and status.

The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, aka the "Lucky Thirteen" issue.

References

CVSS Scores

version 3.1