Homepage

Use of a Broken or Risky Cryptographic Algorithm Affecting java-1.8.0-openjdk-javadoc-zip-debug package, versions <1:1.8.0.131-2.b11.el7_3

Severity

 Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.23% (62nd 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 Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-JAVA180OPENJDKJAVADOCZIPDEBUG-4749112
  • published26 Jul 2021
  • disclosed18 Apr 2017
Report a new vulnerability Found a mistake?

Introduced: 18 Apr 2017

CVE-2017-3539  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:7 java-1.8.0-openjdk-javadoc-zip-debug to version 1:1.8.0.131-2.b11.el7_3 or higher.
This issue was patched in RHSA-2017:1108.

NVD Description

Note: Versions mentioned in the description apply only to the upstream java-1.8.0-openjdk-javadoc-zip-debug package and not the java-1.8.0-openjdk-javadoc-zip-debug package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Security). Supported versions that are affected are Java SE: 6u141, 7u131 and 8u121; Java SE Embedded: 8u121. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Java SE, Java SE Embedded accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.0 Base Score 3.1 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N).