java-1.7.1-ibm-jdbc vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the java-1.7.1-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
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.5.0-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.0-1jpp.1.el7
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.1.5.0-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.5.0-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.0-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.0-1jpp.1.el7
  • H
Resource Exhaustion

<1:1.7.1.4.50-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.50-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.50-1jpp.1.el7
  • H
CVE-2019-2762

<1:1.7.1.4.50-1jpp.1.el7
  • H
Out-of-Bounds

<1:1.7.1.4.50-1jpp.1.el7
  • M
Improper Use of Validation Framework

<1:1.7.1.5.10-1jpp.1.el7
  • M
Integer Underflow

<1:1.7.1.5.10-1jpp.1.el7
  • M
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

<1:1.7.1.5.10-1jpp.1.el7
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.1.5.10-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.10-1jpp.1.el7
  • M
Integer Overflow or Wraparound

<1:1.7.1.5.5-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.5-1jpp.1.el7
  • M
Improper Use of Validation Framework

<1:1.7.1.5.5-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.5-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.5-1jpp.1.el7
  • M
Improper Use of Validation Framework

<1:1.7.1.5.5-1jpp.1.el7
  • M
Deserialization of Untrusted Data

<1:1.7.1.5.5-1jpp.1.el7
  • M
Information Exposure

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

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

<1:1.7.1.5.15-1jpp.1.el7
  • M
Improper Input Validation

<1:1.7.1.4.75-1jpp.1.el7
  • M
CVE-2020-14796

<1:1.7.1.4.75-1jpp.1.el7
  • M
Improper Certificate Validation

<1:1.7.1.4.75-1jpp.1.el7
  • M
Cleartext Transmission of Sensitive Information

<1:1.7.1.4.75-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.75-1jpp.1.el7
  • C
Out-of-Bounds

<1:1.7.1.4.80-1jpp.1.el7
  • C
Time-of-check Time-of-use (TOCTOU)

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

<1:1.7.1.4.70-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.70-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.70-1jpp.1.el7
  • H
Out-of-Bounds

<1:1.7.1.4.70-1jpp.1.el7
  • H
Out-of-Bounds

<1:1.7.1.4.70-1jpp.1.el7
  • H
Uncaught Exception

<1:1.7.1.4.70-1jpp.1.el7
  • H
Uncaught Exception

<1:1.7.1.4.70-1jpp.1.el7
  • H
CVE-2020-14577

<1:1.7.1.4.70-1jpp.1.el7
  • H
Information Exposure

<1:1.7.1.4.70-1jpp.1.el7
  • M
CVE-2021-2432

<1:1.7.1.4.90-1jpp.1.el7
  • M
Improper Verification of Cryptographic Signature

<1:1.7.1.4.90-1jpp.1.el7
  • M
Information Exposure

<1:1.7.1.4.90-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

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

<1:1.7.1.4.60-1jpp.1.el7
  • H
Encoding Error

<1:1.7.1.4.60-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.60-1jpp.1.el7
  • H
Incorrect Regular Expression

<1:1.7.1.4.65-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.65-1jpp.1.el7
  • H
Out-of-Bounds

<1:1.7.1.4.65-1jpp.1.el7
  • H
HTTP Response Splitting

<1:1.7.1.4.65-1jpp.1.el7
  • H
CVE-2020-2781

<1:1.7.1.4.65-1jpp.1.el7
  • H
Uncaught Exception

<1:1.7.1.4.65-1jpp.1.el7
  • H
Uncaught Exception

<1:1.7.1.4.65-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.65-1jpp.1.el7
  • M
Cross-site Scripting (XSS)

<1:1.7.1.4.55-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.55-1jpp.1.el7
  • M
Cross-site Scripting (XSS)

<1:1.7.1.4.55-1jpp.1.el7
  • M
Integer Overflow or Wraparound

<1:1.7.1.4.55-1jpp.1.el7
  • M
Uncaught Exception

<1:1.7.1.4.55-1jpp.1.el7
  • M
Uncaught Exception

<1:1.7.1.4.55-1jpp.1.el7
  • M
CVE-2019-2978

<1:1.7.1.4.55-1jpp.1.el7
  • M
Uncaught Exception

<1:1.7.1.4.55-1jpp.1.el7
  • M
Uncaught Exception

<1:1.7.1.4.55-1jpp.1.el7
  • M
NULL Pointer Dereference

<1:1.7.1.4.55-1jpp.1.el7
  • M
CVE-2019-2945

<1:1.7.1.4.55-1jpp.1.el7
  • C
Inclusion of Functionality from Untrusted Control Sphere

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10243

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10116

<1:1.7.1.4.10-1jpp.3.el7
  • C
Covert Timing Channel

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10110

<1:1.7.1.4.10-1jpp.3.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.10-1jpp.3.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10107

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10105

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10102

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10101

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10096

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10090

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10089

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10087

<1:1.7.1.4.10-1jpp.3.el7
  • C
CVE-2017-10067

<1:1.7.1.4.10-1jpp.3.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.10-1jpp.3.el7
  • H
Out-of-bounds Write

<1:1.7.1.4.45-1jpp.1.el7
  • H
CVE-2019-2697

<1:1.7.1.4.45-1jpp.1.el7
  • H
CVE-2019-2684

<1:1.7.1.4.45-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.45-1jpp.1.el7
  • H
Out-of-bounds Read

<1:1.7.1.4.45-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.40-1jpp.1.el7
  • C
Buffer Overflow

<1:1.7.1.4.40-1jpp.1.el7
  • C
Divide By Zero

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

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • C
Information Exposure

<1:1.7.1.3.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • C
CVE-2015-4903

<1:1.7.1.3.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • C
CVE-2015-4902

<1:1.7.1.3.20-1jpp.1.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.3.20-1jpp.1.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • C
CVE-2015-4883

<1:1.7.1.3.20-1jpp.1.el7
  • C
CVE-2015-4882

<1:1.7.1.3.20-1jpp.1.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • C
CVE-2015-4872

<1:1.7.1.3.20-1jpp.1.el7
  • C
CVE-2015-4871

<1:1.7.1.3.20-1jpp.1.el7
  • C
Insufficient Verification of Data Authenticity

<1:1.7.1.4.15-1jpp.2.el7
  • C
CVE-2015-4860

<1:1.7.1.3.20-1jpp.1.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
CVE-2015-4844

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

<1:1.7.1.4.15-1jpp.2.el7
  • C
Incorrect Conversion between Numeric Types

<1:1.7.1.3.20-1jpp.1.el7
  • C
CVE-2017-10355

<1:1.7.1.4.15-1jpp.2.el7
  • C
Information Exposure

<1:1.7.1.3.20-1jpp.1.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
Out-of-bounds Read

<1:1.7.1.3.20-1jpp.1.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
CVE-2015-4835

<1:1.7.1.3.20-1jpp.1.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
CVE-2015-4810

<1:1.7.1.3.20-1jpp.1.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
Improper Input Validation

<1:1.7.1.3.20-1jpp.1.el7
  • C
CVE-2017-10346

<1:1.7.1.4.15-1jpp.2.el7
  • C
Improper Initialization

<1:1.7.1.3.20-1jpp.1.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
Algorithmic Complexity

<1:1.7.1.3.20-1jpp.1.el7
  • C
HTTP Response Splitting

<1:1.7.1.4.15-1jpp.2.el7
  • C
Information Exposure

<1:1.7.1.3.20-1jpp.1.el7
  • C
CVE-2017-10285

<1:1.7.1.4.15-1jpp.2.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.15-1jpp.2.el7
  • C
Out-of-bounds Read

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

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
Use After Free

<1:1.7.1.4.20-1jpp.1.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.20-1jpp.1.el7
  • H
Improper Access Control

<1:1.7.1.4.20-1jpp.1.el7
  • H
Improper Input Validation

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

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Untrusted Search Path

<1:1.7.1.4.20-1jpp.1.el7
  • H
Use of Insufficiently Random Values

<1:1.7.1.4.20-1jpp.1.el7
  • H
LDAP Injection

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2582

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • M
Improper Input Validation

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

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Improper Input Validation

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Untrusted Search Path

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Improper Authentication

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
XML External Entity (XXE) Injection

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Numeric Errors

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Numeric Errors

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Numeric Errors

<1:1.7.1.4.5-1jpp.1.el7_3
  • M
Numeric Errors

<1:1.7.1.4.5-1jpp.1.el7_3
  • C
CVE-2017-3289

<1:1.7.1.4.1-1jpp.2.el7
  • C
CVE-2017-3272

<1:1.7.1.4.1-1jpp.2.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.1-1jpp.2.el7
  • C
CVE-2017-3259

<1:1.7.1.4.1-1jpp.2.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.1-1jpp.2.el7
  • C
Improper Input Validation

<1:1.7.1.4.1-1jpp.2.el7
  • C
Deserialization of Untrusted Data

<1:1.7.1.4.1-1jpp.2.el7
  • C
Information Exposure

<1:1.7.1.4.1-1jpp.2.el7
  • C
Improper Input Validation

<1:1.7.1.4.1-1jpp.2.el7
  • C
Covert Timing Channel

<1:1.7.1.4.1-1jpp.2.el7
  • C
Covert Timing Channel

<1:1.7.1.4.1-1jpp.2.el7
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.1-1jpp.2.el7
  • C
Improper Input Validation

<1:1.7.1.4.1-1jpp.2.el7
  • C
Use of a Broken or Risky Cryptographic Algorithm

<1:1.7.1.4.1-1jpp.2.el7
  • C
Cleartext Transmission of Sensitive Information

<1:1.7.1.3.60-1jpp.1.el7_2
  • C
Improper Input Validation

<1:1.7.1.3.60-1jpp.1.el7_2
  • C
Improper Access Control

<1:1.7.1.3.60-1jpp.1.el7_2
  • C
CVE-2016-5554

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

<1:1.7.1.3.60-1jpp.1.el7_2
  • C
CVE-2016-3598

<1:1.7.1.3.50-1jpp.1.el7_2
  • C
CVE-2016-3511

<1:1.7.1.3.50-1jpp.1.el7_2
  • C
CVE-2016-3449

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-3443

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-3427

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-3426

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-3422

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-0687

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-0686

<1:1.7.1.3.40-1jpp.1.el7
  • C
CVE-2016-0376

<1:1.7.1.3.40-1jpp.1.el7
  • C
Improper Input Validation

<1:1.7.1.3.40-1jpp.1.el7
  • C
Buffer Overflow

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

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Information Exposure

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
CVE-2015-0491

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Uncaught Exception

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Directory Traversal

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Improperly Implemented Security Check for Standard

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
CVE-2015-0477

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Off-by-one Error

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
CVE-2015-0459

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
CVE-2015-0458

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
CVE-2015-0192

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Use of a Broken or Risky Cryptographic Algorithm

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Directory Traversal

<1:1.7.1.3.0-1jpp.2.el7_1
  • C
Incorrect Conversion between Numeric Types

<1:1.7.1.3.30-1jpp.1.el7
  • C
Out-of-bounds Write

<1:1.7.1.3.30-1jpp.1.el7
  • C
CVE-2016-0466

<1:1.7.1.3.30-1jpp.1.el7
  • C
Information Exposure Through Log Files

<1:1.7.1.3.30-1jpp.1.el7
  • C
CVE-2016-0402

<1:1.7.1.3.30-1jpp.1.el7
  • C
Out-of-bounds Read

<1:1.7.1.3.30-1jpp.1.el7
  • C
Buffer Overflow

<1:1.7.1.3.30-1jpp.1.el7
  • C
Buffer Overflow

<1:1.7.1.3.30-1jpp.1.el7
  • C
Out-of-bounds Read

<1:1.7.1.3.30-1jpp.1.el7
  • C
Improper Data Handling

<1:1.7.1.3.30-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.3.30-1jpp.1.el7
  • C
Out-of-bounds Write

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Missing Release of Resource after Effective Lifetime

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Improper Check for Certificate Revocation

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-4736

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-4733

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

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-4731

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-4729

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

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-2664

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-2638

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-2637

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Integer Overflow or Wraparound

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Improper Certificate Validation

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-2621

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-2619

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Improperly Implemented Security Check for Standard

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Covert Timing Channel

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-2590

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
Cleartext Storage of Sensitive Information

<1:1.7.1.3.10-1jpp.1.el7_1
  • C
CVE-2015-0412

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2015-0408

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2015-0407

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2015-0406

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2015-0403

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2014-8892

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2014-8891

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2014-6593

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
Out-of-bounds Read

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
NULL Pointer Dereference

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
Out-of-bounds Read

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2014-6549

<1:1.7.1.2.10-1jpp.3.el7_0
  • C
CVE-2014-6558

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6532

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6531

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6527

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6515

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
Insufficient Verification of Data Authenticity

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6511

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6506

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6503

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6502

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6493

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6492

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6476

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6458

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6457

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-6456

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-4288

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
Not Failing Securely ('Failing Open')

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
Arbitrary Code Injection

<1:1.7.1.2.0-1jpp.3.el7_0
  • C
CVE-2014-2428

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2427

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2423

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2421

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2420

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2414

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2412

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2409

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2402

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2401

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-2398

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
Insecure Temporary File

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
Cryptographic Issues

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0461

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0460

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0459

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0458

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0457

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0455

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0454

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0453

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0452

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0451

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0449

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0448

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0446

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0429

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0428

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0424

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0423

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0422

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0417

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0416

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0415

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0411

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0410

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0403

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0387

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0376

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0375

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0373

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-0368

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-6954

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
Missing Initialization of a Variable

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5910

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5907

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5899

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5898

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5896

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5889

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5888

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5887

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5884

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2013-5878

<1:1.7.1.1.0-1jpp.2.el7_0
  • C
CVE-2014-4266

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4265

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4263

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4262

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4252

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4244

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4227

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4221

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4220

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4219

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4218

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4209

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
CVE-2014-4208

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
Incorrect Privilege Assignment

<1:1.7.1.1.1-1jpp.1.el7_0
  • C
Credentials Management

<1:1.7.1.1.1-1jpp.1.el7_0
  • M
Resource Exhaustion

*
  • M
Uncontrolled Memory Allocation

*
  • M
Improper Input Validation

*
  • H
Covert Timing Channel

*
  • M
Information Exposure Through Log Files

*
  • M
Improper Input Validation

*
  • M
Race Condition

*
  • M
Deserialization of Untrusted Data

*
  • H
Deserialization of Untrusted Data

*
  • M
Directory Traversal

*
  • L
Improper Input Validation

*
  • M
Improperly Implemented Security Check for Standard

*
  • M
Improper Input Validation

*
  • L
Improper Neutralization of Null Byte or NUL Character

*
  • L
Improper Neutralization of Null Byte or NUL Character

*
  • H
Improper Enforcement of Message Integrity During Transmission in a Communication Channel

*
  • L
Reliance on File Name or Extension of Externally-Supplied File

*
  • M
Deserialization of Untrusted Data

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • M
Resource Exhaustion

*
  • L
Use of Insufficiently Random Values

*
  • L
Integer Coercion Error

*
  • M
Improper Use of Validation Framework

<1:1.7.1.5.10-1jpp.1.el7
  • M
Integer Underflow

<1:1.7.1.5.10-1jpp.1.el7
  • M
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

<1:1.7.1.5.10-1jpp.1.el7
  • M
Resource Exhaustion

*
  • M
Integer Overflow or Wraparound

<1:1.7.1.5.5-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.5-1jpp.1.el7
  • M
Improper Use of Validation Framework

<1:1.7.1.5.5-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.5-1jpp.1.el7
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.1.5.10-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.5-1jpp.1.el7
  • M
Improper Use of Validation Framework

<1:1.7.1.5.5-1jpp.1.el7
  • M
Deserialization of Untrusted Data

<1:1.7.1.5.5-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.5.0-1jpp.1.el7
  • M
Information Exposure

<1:1.7.1.5.5-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.0-1jpp.1.el7
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.1.5.0-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.5.0-1jpp.1.el7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.10-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.5.0-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

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

<1:1.7.1.5.5-1jpp.1.el7
  • M
CVE-2021-2432

<1:1.7.1.4.90-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Integer Overflow or Wraparound

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Untrusted Search Path

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Information Exposure

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Access Control

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Certificate Validation

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

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

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

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

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

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

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

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

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

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • C
Improper Verification of Cryptographic Signature

<1:1.7.1.4.35-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2973

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Directory Traversal

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Authentication

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2940

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • H
Improper Input Validation

<1:1.7.1.4.30-1jpp.1.el7
  • M
Information Exposure

<1:1.7.1.4.90-1jpp.1.el7
  • M
Improper Verification of Cryptographic Signature

<1:1.7.1.4.90-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.30-1jpp.1.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2783

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
Deserialization of Untrusted Data

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2800

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.25-1jpp.3.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
CVE-2018-2657

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.1.4.20-1jpp.1.el7
  • H
Untrusted Search Path

<1:1.7.1.4.20-1jpp.1.el7
  • H
Untrusted Search Path

<1:1.7.1.4.20-1jpp.1.el7
  • H
Untrusted Search Path