Homepage

java-1.8.0-ibm-jdbc vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.8.0-ibm-jdbc package. This does not include vulnerabilities belonging to this package’s dependencies.

How to fix?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

Fix for free
VulnerabilityVulnerable Version
  • C
Integer Overflow or Wraparound

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Untrusted Search Path

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Information Exposure

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Improper Access Control

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Improper Certificate Validation

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Improper Verification of Cryptographic Signature

<1:1.8.0.5.25-1jpp.1.el6_10
  • C
Improper Access Control

<1:1.8.0.5.25-1jpp.1.el6_10
  • H
CVE-2018-2973

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
Directory Traversal

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
Improper Authentication

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
Information Exposure

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
CVE-2018-2940

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
Improper Input Validation

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.20-1jpp.1.el6_10
  • H
CVE-2018-2783

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Deserialization of Untrusted Data

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
CVE-2018-2800

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Improper Verification of Cryptographic Signature

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.15-1jpp.2.el6_9
  • H
Incorrect Calculation

<1:1.8.0.5.20-1jpp.1.el6_10
  • C
CVE-2018-2638

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
CVE-2018-2639

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Incorrect Permission Assignment for Critical Resource

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Untrusted Search Path

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Deserialization of Untrusted Data

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
CVE-2018-2582

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Improper Access Control

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Improper Input Validation

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Use of Insufficiently Random Values

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Improper Input Validation

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
LDAP Injection

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Use After Free

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
CVE-2017-10309

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
CVE-2017-10355

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Insufficient Verification of Data Authenticity

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
CVE-2017-10346

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
CVE-2017-10285

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
HTTP Response Splitting

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
CVE-2017-10105

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
Inclusion of Functionality from Untrusted Control Sphere

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10096

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10090

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10067

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10110

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10101

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10102

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10107

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10078

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10116

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10243

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10087

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
CVE-2017-10089

<1:1.8.0.4.10-1jpp.1.el6_9
  • C
Covert Timing Channel

<1:1.8.0.4.10-1jpp.1.el6_9
  • M
Numeric Errors

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Numeric Errors

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Numeric Errors

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Numeric Errors

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
XML External Entity (XXE) Injection

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Improper Input Validation

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Improper Input Validation

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Improper Authentication

<1:1.8.0.4.5-1jpp.1.el6_9
  • M
Untrusted Search Path

<1:1.8.0.4.5-1jpp.1.el6_9
  • C
CVE-2017-3259

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Covert Timing Channel

<1:1.8.0.4.0-1jpp.1.el6_8
  • M
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.4.1-1jpp.1.el6_8
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
CVE-2017-3272

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Information Exposure

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Integer Overflow or Wraparound

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
CVE-2017-3289

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Deserialization of Untrusted Data

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Improper Input Validation

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Improper Input Validation

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Allocation of Resources Without Limits or Throttling

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Covert Timing Channel

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
Improper Input Validation

<1:1.8.0.4.0-1jpp.1.el6_8
  • C
CVE-2016-5554

<1:1.8.0.3.20-1jpp.1.el6_8
  • C
Improper Access Control

<1:1.8.0.3.20-1jpp.1.el6_8
  • C
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.3.20-1jpp.1.el6_8
  • C
Cleartext Transmission of Sensitive Information

<1:1.8.0.3.20-1jpp.1.el6_8
  • C
Improper Input Validation

<1:1.8.0.3.20-1jpp.1.el6_8
  • C
Out-of-bounds Read

<1:1.8.0.5.5-1jpp.1.el6_9
  • C
CVE-2016-3511

<1:1.8.0.3.10-1jpp.2.el6_8
  • C
CVE-2016-3598

<1:1.8.0.3.10-1jpp.2.el6_8
  • C
CVE-2016-3422

<1:1.8.0.3.0-1jpp.1.el6
  • C
Buffer Overflow

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-3443

<1:1.8.0.3.0-1jpp.1.el6
  • C
Improper Input Validation

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-3449

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-0376

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-3426

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-3427

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-0687

<1:1.8.0.3.0-1jpp.1.el6
  • C
CVE-2016-0686

<1:1.8.0.3.0-1jpp.1.el6
  • H
CVE-2016-0705

<1:1.8.0.5.20-1jpp.1.el6_10
  • M
Information Exposure

*
  • M
Uncaught Exception

*
  • M
Uncaught Exception

*
  • H
Out-of-Bounds

*
  • M
Improper Input Validation

*
  • L
CVE-2020-14577

*
  • H
Out-of-Bounds

*
  • M
CVE-2020-14556

*
  • H
Out-of-Bounds

<1:1.8.0.6.10-1jpp.1.el6_10
  • M
Uncaught Exception

*
  • H
Improper Input Validation

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
CVE-2020-2781

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
Uncaught Exception

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
Uncaught Exception

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
Uncaught Exception

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
HTTP Response Splitting

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
Uncaught Exception

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
Incorrect Regular Expression

<1:1.8.0.6.10-1jpp.1.el6_10
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.6.5-1jpp.1.el6_10
  • H
Use of a Broken or Risky Cryptographic Algorithm

*
  • H
Encoding Error

<1:1.8.0.6.5-1jpp.1.el6_10
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.6.5-1jpp.1.el6_10
  • H
Modification of Assumed-Immutable Data (MAID)

<1:1.8.0.6.5-1jpp.1.el6_10
  • M
Improper Input Validation

*
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.6.10-1jpp.1.el6_10
  • M
CVE-2019-2996

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Improper Authorization

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Allocation of Resources Without Limits or Throttling

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Cross-site Scripting (XSS)

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Uncaught Exception

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
CVE-2019-2945

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Uncaught Exception

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Uncaught Exception

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Integer Overflow or Wraparound

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Uncaught Exception

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Uncaught Exception

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
CVE-2019-2978

<1:1.8.0.6.0-1jpp.1.el6_10
  • M
Cross-site Scripting (XSS)

<1:1.8.0.6.0-1jpp.1.el6_10
  • H
Insufficiently Protected Credentials

<1:1.8.0.6.10-1jpp.1.el6_10
  • M
NULL Pointer Dereference

<1:1.8.0.6.0-1jpp.1.el6_10
  • H
Out-of-Bounds

<1:1.8.0.5.40-1jpp.1.el6_10
  • H
Out-of-Bounds

<1:1.8.0.5.40-1jpp.1.el6_10
  • H
CVE-2019-2762

<1:1.8.0.5.40-1jpp.1.el6_10
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.40-1jpp.1.el6_10
  • H
Improper Input Validation

<1:1.8.0.5.40-1jpp.1.el6_10
  • H
CVE-2019-2786

<1:1.8.0.5.40-1jpp.1.el6_10
  • H
Resource Exhaustion

<1:1.8.0.5.40-1jpp.1.el6_10
  • C
Buffer Overflow

<1:1.8.0.5.30-1jpp.1.el6_10
  • H
Out-of-bounds Read

<1:1.8.0.5.35-1jpp.1.el6_10
  • C
Information Exposure

<1:1.8.0.5.30-1jpp.1.el6_10
  • C
CVE-2019-2449

<1:1.8.0.5.30-1jpp.1.el6_10
  • H
CVE-2019-2697

<1:1.8.0.5.35-1jpp.1.el6_10
  • C
Improper Input Validation

<1:1.8.0.5.30-1jpp.1.el6_10
  • C
Divide By Zero

<1:1.8.0.5.30-1jpp.1.el6_10
  • H
Out-of-bounds Write

<1:1.8.0.5.35-1jpp.1.el6_10
  • H
CVE-2019-2684

<1:1.8.0.5.35-1jpp.1.el6_10
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.5.35-1jpp.1.el6_10