Homepage

java-1.7.0-openjdk-devel vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.7.0-openjdk-devel 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
  • M
Improper Input Validation

*
  • M
CVE-2024-21131

*
  • M
CVE-2024-21140

*
  • M
Out-of-bounds Read

*
  • H
CVE-2024-21147

*
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

*
  • M
Integer Overflow or Wraparound

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • M
Integer Overflow or Wraparound

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • M
Deserialization of Untrusted Data

*
  • M
Improper Use of Validation Framework

*
  • M
Improper Output Neutralization for Logs

*
  • M
Out-of-bounds Write

*
  • M
Uncontrolled Memory Allocation

*
  • M
Integer Overflow or Wraparound

*
  • M
Improper Input Validation

*
  • H
Covert Timing Channel

*
  • M
Improper Input Validation

*
  • M
Information Exposure Through Log Files

*
  • M
Improper Input Validation

*
  • H
Integer Overflow or Wraparound

*
  • M
Improper Certificate Validation

*
  • M
Deserialization of Untrusted Data

*
  • L
Out-of-bounds Read

*
  • 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

*
  • M
Information Exposure

*
  • 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

*
  • H
Integer Coercion Error

*
  • M
Improper Access Control

*
  • M
Resource Leak

*
  • M
CVE-2017-10176

*
  • M
Covert Timing Channel

*
  • M
CVE-2015-2596

*
  • M
Improper Use of Validation Framework

*
  • H
Incorrect Behavior Order: Early Validation

*
  • M
Integer Underflow

*
  • M
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

*
  • M
Resource Exhaustion

*
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

*
  • M
Improper Authorization

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • M
Improper Use of Validation Framework

*
  • M
Uncaught Exception

*
  • M
Improper Cross-boundary Removal of Sensitive Data

*
  • H
Untrusted Search Path

<1:1.7.0.201-2.6.16.1.el7_6
  • H
Information Exposure

<1:1.7.0.201-2.6.16.1.el7_6
  • H
Improper Access Control

<1:1.7.0.201-2.6.16.1.el7_6
  • H
Improper Certificate Validation

<1:1.7.0.201-2.6.16.1.el7_6
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.0.201-2.6.16.1.el7_6
  • H
Improper Verification of Cryptographic Signature

<1:1.7.0.201-2.6.16.1.el7_6
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.0.191-2.6.15.4.el7_5
  • H
Sensitive Information Uncleared Before Release

<1:1.7.0.181-2.6.14.8.el7_5
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.181-2.6.14.5.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.181-2.6.14.5.el7
  • H
CVE-2018-2814

<1:1.7.0.181-2.6.14.5.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.181-2.6.14.5.el7
  • H
Deserialization of Untrusted Data

<1:1.7.0.181-2.6.14.5.el7
  • H
CVE-2018-2800

<1:1.7.0.181-2.6.14.5.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.181-2.6.14.5.el7
  • H
Improper Verification of Cryptographic Signature

<1:1.7.0.181-2.6.14.5.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.181-2.6.14.5.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.181-2.6.14.5.el7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Untrusted Search Path

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Deserialization of Untrusted Data

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Improper Access Control

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Improper Input Validation

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Use After Free

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Use of a Broken or Risky Cryptographic Algorithm

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Use of Insufficiently Random Values

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Improper Input Validation

<1:1.7.0.171-2.6.13.0.el7_4
  • H
LDAP Injection

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Use After Free

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.171-2.6.13.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • H
CVE-2017-10355

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Insufficient Verification of Data Authenticity

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Use of a Broken or Risky Cryptographic Algorithm

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • H
CVE-2017-10274

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • H
CVE-2017-10346

<1:1.7.0.161-2.6.12.0.el7_4
  • H
CVE-2017-10285

<1:1.7.0.161-2.6.12.0.el7_4
  • H
HTTP Response Splitting

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.161-2.6.12.0.el7_4
  • C
CVE-2017-10096

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10090

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10067

<1:1.7.0.151-2.6.11.1.el7_4
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10110

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10101

<1:1.7.0.151-2.6.11.1.el7_4
  • C
Covert Timing Channel

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10102

<1:1.7.0.151-2.6.11.1.el7_4
  • H
CVE-2017-10193

<1:1.7.0.161-2.6.12.0.el7_4
  • C
CVE-2017-10107

<1:1.7.0.151-2.6.11.1.el7_4
  • H
CVE-2017-10198

<1:1.7.0.161-2.6.12.0.el7_4
  • C
CVE-2017-10116

<1:1.7.0.151-2.6.11.1.el7_4
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10081

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10243

<1:1.7.0.151-2.6.11.1.el7_4
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.0.151-2.6.11.1.el7_4
  • C
Integer Overflow or Wraparound

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10087

<1:1.7.0.151-2.6.11.1.el7_4
  • C
CVE-2017-10089

<1:1.7.0.151-2.6.11.1.el7_4
  • C
Covert Timing Channel

<1:1.7.0.151-2.6.11.1.el7_4
  • M
Improper Input Validation

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

<1:1.7.0.141-2.6.10.1.el7_3
  • M
Improper Input Validation

<1:1.7.0.141-2.6.10.1.el7_3
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.0.141-2.6.10.1.el7_3
  • M
Improper Authentication

<1:1.7.0.141-2.6.10.1.el7_3
  • M
Untrusted Search Path

<1:1.7.0.141-2.6.10.1.el7_3
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.0.131-2.6.9.0.el7_3
  • C
CVE-2017-3272

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Information Exposure

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Integer Overflow or Wraparound

<1:1.7.0.131-2.6.9.0.el7_3
  • C
CVE-2017-3289

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Deserialization of Untrusted Data

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Improper Input Validation

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Improper Input Validation

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Covert Timing Channel

<1:1.7.0.131-2.6.9.0.el7_3
  • C
Improper Input Validation

<1:1.7.0.131-2.6.9.0.el7_3
  • H
CVE-2016-5554

<1:1.7.0.121-2.6.8.0.el7_3
  • H
Access of Resource Using Incompatible Type ('Type Confusion')

<1:1.7.0.121-2.6.8.0.el7_3
  • H
Use of a Broken or Risky Cryptographic Algorithm

<1:1.7.0.121-2.6.8.0.el7_3
  • H
Cleartext Transmission of Sensitive Information

<1:1.7.0.121-2.6.8.0.el7_3
  • H
Improper Input Validation

<1:1.7.0.121-2.6.8.0.el7_3
  • H
Out-of-bounds Read

<1:1.7.0.121-2.6.8.0.el7_3
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.111-2.6.7.2.el7_2
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.111-2.6.7.2.el7_2
  • H
CVE-2016-3458

<1:1.7.0.111-2.6.7.2.el7_2
  • H
Integer Overflow or Wraparound

<1:1.7.0.111-2.6.7.2.el7_2
  • H
CVE-2016-3610

<1:1.7.0.111-2.6.7.2.el7_2
  • H
CVE-2016-3606

<1:1.7.0.111-2.6.7.2.el7_2
  • H
CVE-2016-3598

<1:1.7.0.111-2.6.7.2.el7_2
  • C
CVE-2016-3427

<1:1.7.0.101-2.6.6.1.el7_2
  • C
CVE-2016-0687

<1:1.7.0.101-2.6.6.1.el7_2
  • C
CVE-2016-3425

<1:1.7.0.101-2.6.6.1.el7_2
  • C
CVE-2016-0686

<1:1.7.0.101-2.6.6.1.el7_2
  • C
CVE-2016-0695

<1:1.7.0.101-2.6.6.1.el7_2
  • H
Improperly Implemented Security Check for Standard

<1:1.7.0.99-2.6.5.0.el7_2
  • H
Improper Data Handling

<1:1.7.0.95-2.6.4.0.el7_2
  • H
Incorrect Conversion between Numeric Types

<1:1.7.0.95-2.6.4.0.el7_2
  • H
CVE-2016-0402

<1:1.7.0.95-2.6.4.0.el7_2
  • H
CVE-2016-0466

<1:1.7.0.95-2.6.4.0.el7_2
  • H
Out-of-bounds Write

<1:1.7.0.95-2.6.4.0.el7_2
  • H
Information Exposure Through Log Files

<1:1.7.0.95-2.6.4.0.el7_2
  • H
CVE-2015-4871

<1:1.7.0.95-2.6.4.0.el7_2
  • C
Out-of-bounds Read

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4844

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4883

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Information Exposure

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4882

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4911

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Algorithmic Complexity

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Information Exposure

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Incorrect Conversion between Numeric Types

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4835

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Allocation of Resources Without Limits or Throttling

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4860

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Improper Initialization

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4881

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4903

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Improper Input Validation

<1:1.7.0.91-2.6.2.1.el7_1
  • C
CVE-2015-4872

<1:1.7.0.91-2.6.2.1.el7_1
  • C
Improper Certificate Validation

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Out-of-bounds Write

<1:1.7.0.85-2.6.1.2.el7_1
  • C
CVE-2015-2621

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Improper Check for Certificate Revocation

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Access of Resource Using Incompatible Type ('Type Confusion')

<1:1.7.0.85-2.6.1.2.el7_1
  • C
CVE-2015-4733

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Missing Release of Resource after Effective Lifetime

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Covert Timing Channel

<1:1.7.0.85-2.6.1.2.el7_1
  • C
CVE-2015-2590

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Integer Overflow or Wraparound

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

<1:1.7.0.85-2.6.1.2.el7_1
  • C
CVE-2015-4731

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

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

<1:1.7.0.85-2.6.1.2.el7_1
  • C
Directory Traversal

<1:1.7.0.79-2.5.5.1.el7_1
  • C
Uncaught Exception

<1:1.7.0.79-2.5.5.1.el7_1
  • C
Off-by-one Error

<1:1.7.0.79-2.5.5.1.el7_1
  • C
Directory Traversal

<1:1.7.0.79-2.5.5.1.el7_1
  • C
CVE-2015-0460

<1:1.7.0.79-2.5.5.1.el7_1
  • C
CVE-2015-0477

<1:1.7.0.79-2.5.5.1.el7_1
  • C
Improperly Implemented Security Check for Standard

<1:1.7.0.79-2.5.5.1.el7_1
  • C
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.7.0.75-2.5.4.2.el7_0
  • C
CVE-2014-6593

<1:1.7.0.75-2.5.4.2.el7_0
  • C
Out-of-bounds Read

<1:1.7.0.75-2.5.4.2.el7_0
  • C
CVE-2015-0408

<1:1.7.0.75-2.5.4.2.el7_0
  • C
CVE-2015-0407

<1:1.7.0.75-2.5.4.2.el7_0
  • C
NULL Pointer Dereference

<1:1.7.0.75-2.5.4.2.el7_0
  • C
CVE-2015-0395

<1:1.7.0.75-2.5.4.2.el7_0
  • C
CVE-2014-6601

<1:1.7.0.75-2.5.4.2.el7_0
  • C
Insecure Temporary File

<1:1.7.0.75-2.5.4.2.el7_0
  • C
CVE-2015-0412

<1:1.7.0.75-2.5.4.2.el7_0
  • C
Out-of-bounds Read

<1:1.7.0.75-2.5.4.2.el7_0
  • C
Not Failing Securely ('Failing Open')

<1:1.7.0.75-2.5.4.2.el7_0
  • H
CVE-2014-6506

<1:1.7.0.71-2.5.3.1.el7_0
  • H
Insufficient Verification of Data Authenticity

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6504

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6502

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6511

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6517

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6519

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6531

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6457

<1:1.7.0.71-2.5.3.1.el7_0
  • H
CVE-2014-6558

<1:1.7.0.71-2.5.3.1.el7_0
  • C
CVE-2014-4252

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4216

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4209

<1:1.7.0.65-2.5.1.2.el7_0
  • C
Use of Externally-Controlled Format String

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4263

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4221

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4223

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4218

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-2483

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4262

<1:1.7.0.65-2.5.1.2.el7_0
  • C
CVE-2014-4219

<1:1.7.0.65-2.5.1.2.el7_0
  • H
Out-of-Bounds

<1:1.7.0.261-2.6.22.2.el7_8
  • H
Uncaught Exception

<1:1.7.0.261-2.6.22.2.el7_8
  • H
Improper Input Validation

<1:1.7.0.261-2.6.22.2.el7_8
  • C
CVE-2014-4244

<1:1.7.0.65-2.5.1.2.el7_0
  • H
CVE-2020-2781

<1:1.7.0.261-2.6.22.2.el7_8
  • C
CVE-2014-4266

<1:1.7.0.65-2.5.1.2.el7_0
  • H
Uncaught Exception

<1:1.7.0.261-2.6.22.2.el7_8
  • H
HTTP Response Splitting

<1:1.7.0.261-2.6.22.2.el7_8
  • H
Uncaught Exception

<1:1.7.0.261-2.6.22.2.el7_8
  • H
Incorrect Regular Expression

<1:1.7.0.261-2.6.22.2.el7_8
  • C
CVE-2014-0454

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0455

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2414

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2421

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0453

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0452

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0460

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2402

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0429

<1:1.7.0.55-2.4.7.2.el7_0
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.251-2.6.21.0.el7_7
  • C
CVE-2014-2397

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0461

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2398

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2412

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0457

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0458

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2427

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0446

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2413

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0459

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2423

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-2403

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0456

<1:1.7.0.55-2.4.7.2.el7_0
  • C
CVE-2014-0451

<1:1.7.0.55-2.4.7.2.el7_0
  • C
Insecure Temporary File

<1:1.7.0.55-2.4.7.2.el7_0
  • H
Use of a Broken or Risky Cryptographic Algorithm

<1:1.7.0.251-2.6.21.0.el7_7
  • H
Encoding Error

<1:1.7.0.251-2.6.21.0.el7_7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.251-2.6.21.0.el7_7
  • H
Modification of Assumed-Immutable Data (MAID)

<1:1.7.0.251-2.6.21.0.el7_7
  • H
Improper Input Validation

<1:1.7.0.251-2.6.21.0.el7_7
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.251-2.6.21.0.el7_7
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Cross-site Scripting (XSS)

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Uncaught Exception

<1:1.7.0.241-2.6.20.0.el7_7
  • M
CVE-2019-2945

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Uncaught Exception

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Uncaught Exception

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Integer Overflow or Wraparound

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Uncaught Exception

<1:1.7.0.241-2.6.20.0.el7_7
  • M
CVE-2019-2978

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Cross-site Scripting (XSS)

<1:1.7.0.241-2.6.20.0.el7_7
  • M
NULL Pointer Dereference

<1:1.7.0.241-2.6.20.0.el7_7
  • M
Improper Input Validation

<1:1.7.0.241-2.6.20.0.el7_7
  • M
CVE-2019-2762

<1:1.7.0.231-2.6.19.1.el7_6
  • M
Covert Timing Channel

<1:1.7.0.231-2.6.19.1.el7_6
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.0.231-2.6.19.1.el7_6
  • M
Improper Input Validation

<1:1.7.0.231-2.6.19.1.el7_6
  • M
CVE-2019-2786

<1:1.7.0.231-2.6.19.1.el7_6
  • M
Out-of-Bounds

<1:1.7.0.231-2.6.19.1.el7_6
  • M
Information Exposure

<1:1.7.0.211-2.6.17.1.el7_6
  • H
Out-of-bounds Write

<1:1.7.0.221-2.6.18.0.el7_6
  • H
CVE-2019-2684

<1:1.7.0.221-2.6.18.0.el7_6
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.221-2.6.18.0.el7_6