Homepage

java-1.8.0-openjdk vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.8.0-openjdk 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 Certificate Validation

<1:1.8.0.392.b08-2.82.amzn1
  • M
Deserialization of Untrusted Data

<1:1.8.0.392.b08-2.82.amzn1
  • H
Resource Exhaustion

<1:1.8.0.382.b05-1.79.amzn1
  • H
Out-of-Bounds

<1:1.8.0.252.b09-2.51.amzn1
  • H
Uncaught Exception

<1:1.8.0.252.b09-2.51.amzn1
  • H
Incorrect Regular Expression

<1:1.8.0.252.b09-2.51.amzn1
  • H
Uncaught Exception

<1:1.8.0.252.b09-2.51.amzn1
  • H
Uncaught Exception

<1:1.8.0.252.b09-2.51.amzn1
  • H
CVE-2020-2781

<1:1.8.0.252.b09-2.51.amzn1
  • H
Improper Input Validation

<1:1.8.0.252.b09-2.51.amzn1
  • H
HTTP Response Splitting

<1:1.8.0.252.b09-2.51.amzn1
  • H
Uncaught Exception

<1:1.8.0.252.b09-2.51.amzn1
  • H
Uncaught Exception

<1:1.8.0.252.b09-2.51.amzn1
  • M
CVE-2023-22043

<1:1.8.0.382.b05-1.78.amzn1
  • M
Directory Traversal

<1:1.8.0.382.b05-1.78.amzn1
  • M
Improperly Implemented Security Check for Standard

<1:1.8.0.382.b05-1.78.amzn1
  • H
Improper Enforcement of Message Integrity During Transmission in a Communication Channel

<1:1.8.0.372.b07-1.76.amzn1
  • M
Improper Input Validation

<1:1.8.0.382.b05-1.78.amzn1
  • M
Improper Neutralization of Null Byte or NUL Character

<1:1.8.0.382.b05-1.78.amzn1
  • M
Information Exposure

<1:1.8.0.382.b05-1.78.amzn1
  • M
Out-of-bounds Read

<1:1.8.0.382.b05-1.78.amzn1
  • M
Improper Input Validation

<1:1.8.0.382.b05-1.78.amzn1
  • M
Improper Neutralization of Null Byte or NUL Character

<1:1.8.0.382.b05-1.78.amzn1
  • M
Use of Insufficiently Random Values

<1:1.8.0.362.b08-1.72.amzn1
  • M
Reliance on File Name or Extension of Externally-Supplied File

<1:1.8.0.362.b08-1.72.amzn1
  • M
Deserialization of Untrusted Data

<1:1.8.0.362.b08-1.72.amzn1
  • M
Resource Exhaustion

<1:1.8.0.362.b08-1.72.amzn1
  • M
Resource Exhaustion

<1:1.8.0.352.b08-2.70.amzn1
  • M
Integer Coercion Error

<1:1.8.0.352.b08-2.70.amzn1
  • M
Use of Insufficiently Random Values

<1:1.8.0.352.b08-2.70.amzn1
  • M
Allocation of Resources Without Limits or Throttling

<1:1.8.0.352.b08-2.70.amzn1
  • H
Integer Coercion Error

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Access Control

<1:1.8.0.342.b07-0.68.amzn1
  • H
Integer Overflow or Wraparound

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Use of Validation Framework

<1:1.8.0.342.b07-0.68.amzn1
  • H
Incorrect Behavior Order: Early Validation

<1:1.8.0.342.b07-0.68.amzn1
  • H
Integer Underflow

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Use of Validation Framework

<1:1.8.0.342.b07-0.68.amzn1
  • H
Resource Leak

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Input Validation

<1:1.8.0.342.b07-0.68.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.342.b07-0.68.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.342.b07-0.68.amzn1
  • H
Resource Exhaustion

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Use of Validation Framework

<1:1.8.0.342.b07-0.68.amzn1
  • H
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

<1:1.8.0.342.b07-0.68.amzn1
  • H
Integer Overflow or Wraparound

<1:1.8.0.342.b07-0.68.amzn1
  • H
Uncaught Exception

<1:1.8.0.342.b07-0.68.amzn1
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.8.0.342.b07-0.68.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Cross-boundary Removal of Sensitive Data

<1:1.8.0.342.b07-0.68.amzn1
  • H
Deserialization of Untrusted Data

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Authorization

<1:1.8.0.342.b07-0.68.amzn1
  • H
Improper Input Validation

<1:1.8.0.312.b07-0.65.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.312.b07-0.65.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.312.b07-0.65.amzn1
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.8.0.312.b07-0.65.amzn1
  • H
NULL Pointer Dereference

<1:1.8.0.312.b07-0.65.amzn1
  • H
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.312.b07-0.65.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.312.b07-0.65.amzn1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.8.0.312.b07-0.65.amzn1
  • H
Information Exposure

<1:1.8.0.312.b07-0.65.amzn1
  • H
Incorrect Authorization

<1:1.8.0.312.b07-0.65.amzn1
  • H
Improper Input Validation

<1:1.8.0.312.b07-0.65.amzn1
  • C
Deserialization of Untrusted Data

<1:1.8.0.312.b07-0.66.amzn1
  • C
Deserialization of Untrusted Data

<1:1.8.0.312.b07-0.66.amzn1
  • H
CVE-2021-2388

<1:1.8.0.302.b08-0.67.amzn1
  • H
CVE-2021-2341

<1:1.8.0.302.b08-0.67.amzn1
  • H
CVE-2021-2369

<1:1.8.0.302.b08-0.67.amzn1
  • M
CVE-2021-2163

<1:1.8.0.292.b10-1.63.amzn1
  • M
CVE-2020-14792

<1:1.8.0.272.b10-1.56.amzn1
  • M
CVE-2020-14797

<1:1.8.0.272.b10-1.56.amzn1
  • M
CVE-2020-14803

<1:1.8.0.272.b10-1.56.amzn1
  • M
CVE-2020-14781

<1:1.8.0.272.b10-1.56.amzn1
  • M
CVE-2020-14779

<1:1.8.0.272.b10-1.56.amzn1
  • M
CVE-2020-14782

<1:1.8.0.272.b10-1.56.amzn1
  • M
CVE-2020-14796

<1:1.8.0.272.b10-1.56.amzn1
  • H
CVE-2020-14583

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-14621

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-14578

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-14579

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-14577

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-14593

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-14556

<1:1.8.0.265.b01-0.54.amzn1
  • H
CVE-2020-2601

<1:1.8.0.242.b08-0.50.amzn1
  • H
CVE-2020-2590

<1:1.8.0.242.b08-0.50.amzn1
  • H
Deserialization of Untrusted Data

<1:1.8.0.242.b08-0.50.amzn1
  • H
CVE-2020-2659

<1:1.8.0.242.b08-0.50.amzn1
  • H
CVE-2020-2593

<1:1.8.0.242.b08-0.50.amzn1
  • H
CVE-2020-2654

<1:1.8.0.242.b08-0.50.amzn1
  • H
Improper Handling of Exceptional Conditions

<1:1.8.0.242.b08-0.50.amzn1
  • H
CVE-2019-2999

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2989

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2981

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2988

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2975

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2987

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2983

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2973

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2949

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2945

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2992

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2962

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2964

<1:1.8.0.232.b09-0.48.amzn1
  • H
CVE-2019-2978

<1:1.8.0.232.b09-0.48.amzn1
  • M
CVE-2019-2816

<1:1.8.0.222.b10-0.47.amzn1
  • M
CVE-2019-2745

<1:1.8.0.222.b10-0.47.amzn1
  • M
CVE-2019-2762

<1:1.8.0.222.b10-0.47.amzn1
  • M
CVE-2019-2786

<1:1.8.0.222.b10-0.47.amzn1
  • H
CVE-2019-2684

<1:1.8.0.212.b04-0.45.amzn1
  • M
CVE-2019-2769

<1:1.8.0.222.b10-0.47.amzn1
  • M
CVE-2019-2842

<1:1.8.0.222.b10-0.47.amzn1
  • H
Resource Exhaustion

<1:1.8.0.212.b04-0.45.amzn1
  • H
CVE-2019-2698

<1:1.8.0.212.b04-0.45.amzn1
  • C
CVE-2018-3214

<1:1.8.0.191.b12-0.42.amzn1
  • C
CVE-2018-3180

<1:1.8.0.191.b12-0.42.amzn1
  • C
CVE-2018-3169

<1:1.8.0.191.b12-0.42.amzn1
  • C
CVE-2018-3136

<1:1.8.0.191.b12-0.42.amzn1
  • C
CVE-2018-3183

<1:1.8.0.191.b12-0.42.amzn1
  • C
CVE-2018-3149

<1:1.8.0.191.b12-0.42.amzn1
  • C
CVE-2018-3139

<1:1.8.0.191.b12-0.42.amzn1
  • M
CVE-2018-2952

<1:1.8.0.181-8.b13.39.39.amzn1
  • H
Information Exposure

<1:1.8.0.171-8.b10.38.amzn1
  • C
CVE-2018-2800

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2799

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2815

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2814

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2796

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2794

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2798

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2790

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2795

<1:1.8.0.171-7.b10.37.amzn1
  • C
CVE-2018-2797

<1:1.8.0.171-7.b10.37.amzn1
  • H
CVE-2018-2678

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2637

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2677

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2629

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2633

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2603

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2618

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2602

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2663

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2641

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2634

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2582

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2588

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2599

<1:1.8.0.161-0.b14.36.amzn1
  • H
CVE-2018-2579

<1:1.8.0.161-0.b14.36.amzn1
  • C
CVE-2017-10348

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10349

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10357

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10388

<1:1.8.0.151-1.b12.35.amzn1
  • C
Information Exposure

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10347

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10345

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10355

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10295

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10274

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10346

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10281

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10285

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10350

<1:1.8.0.151-1.b12.35.amzn1
  • C
CVE-2017-10096

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10109

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10198

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10111

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10135

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10108

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10110

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10107

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10102

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10101

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10116

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10067

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10090

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10053

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10074

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10193

<1:1.8.0.141-1.b16.32.amzn1
  • C
CVE-2017-10115

<1:1.8.0.141-1.b16.32.amzn1
  • M
CVE-2017-3526

<1:1.8.0.131-2.b11.30.amzn1
  • M
CVE-2017-3544

<1:1.8.0.131-2.b11.30.amzn1
  • M
CVE-2017-3511

<1:1.8.0.131-2.b11.30.amzn1
  • M
CVE-2017-3533

<1:1.8.0.131-2.b11.30.amzn1
  • M
CVE-2017-3509

<1:1.8.0.131-2.b11.30.amzn1
  • M
CVE-2017-3539

<1:1.8.0.131-2.b11.30.amzn1
  • M
CVE-2016-5542

<1:1.8.0.131-2.b11.30.amzn1
  • C
CVE-2016-5548

<1:1.8.0.121-0.b13.29.amzn1
  • C
Information Exposure

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2017-3253

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2017-3289

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2017-3272

<1:1.8.0.121-0.b13.29.amzn1
  • C
Improper Input Validation

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2017-3252

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2016-5546

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2016-5547

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2016-5552

<1:1.8.0.121-0.b13.29.amzn1
  • C
Information Exposure

<1:1.8.0.121-0.b13.29.amzn1
  • C
CVE-2017-3261

<1:1.8.0.121-0.b13.29.amzn1
  • C
Cleartext Transmission of Sensitive Information

<1:1.8.0.111-1.b15.25.amzn1
  • C
Access Restriction Bypass

<1:1.8.0.111-1.b15.25.amzn1
  • C
CVE-2016-5542

<1:1.8.0.111-1.b15.25.amzn1
  • C
CVE-2016-5554

<1:1.8.0.111-1.b15.25.amzn1
  • C
Access of Resource Using Incompatible Type ('Type Confusion')

<1:1.8.0.111-1.b15.25.amzn1
  • C
CVE-2016-3610

<1:1.8.0.101-3.b13.24.amzn1
  • C
Integer Overflow or Wraparound

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3606

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3508

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3500

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3587

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3598

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3458

<1:1.8.0.101-3.b13.24.amzn1
  • C
CVE-2016-3427

<1:1.8.0.91-0.b14.10.amzn1
  • C
CVE-2016-3426

<1:1.8.0.91-0.b14.10.amzn1
  • C
CVE-2016-0686

<1:1.8.0.91-0.b14.10.amzn1
  • C
CVE-2016-0695

<1:1.8.0.91-0.b14.10.amzn1
  • C
CVE-2016-3425

<1:1.8.0.91-0.b14.10.amzn1
  • C
CVE-2016-0687

<1:1.8.0.91-0.b14.10.amzn1
  • C
CVE-2016-0636

<1:1.8.0.77-0.b03.9.amzn1
  • H
CVE-2016-0494

<1:1.8.0.71-2.b15.8.amzn1
  • H
CVE-2016-0483

<1:1.8.0.71-2.b15.8.amzn1
  • H
CVE-2016-0448

<1:1.8.0.71-2.b15.8.amzn1
  • H
CVE-2016-0475

<1:1.8.0.71-2.b15.8.amzn1
  • H
Improper Data Handling

<1:1.8.0.71-2.b15.8.amzn1
  • H
CVE-2016-0466

<1:1.8.0.71-2.b15.8.amzn1
  • H
CVE-2016-0402

<1:1.8.0.71-2.b15.8.amzn1
  • H
CVE-2015-4903

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4911

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4893

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4881

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4883

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4882

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4872

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4860

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4868

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4844

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4842

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4806

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4843

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4840

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4835

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4734

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4805

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4803

<1:1.8.0.65-2.b17.7.amzn1
  • H
CVE-2015-4749

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-4748

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-4760

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-4732

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-4733

<1:1.8.0.51-1.b16.6.amzn1
  • H
Cryptographic Issues

<1:1.8.0.51-1.b16.6.amzn1
  • H
Link Following

<1:1.8.0.51-1.b16.6.amzn1
  • H
Use of a Broken or Risky Cryptographic Algorithm

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2659

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-4731

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2632

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2625

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2621

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2628

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2601

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-0383

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-2590

<1:1.8.0.51-1.b16.6.amzn1
  • H
CVE-2015-0480

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0488

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0477

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2005-1080

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0478

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0460

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0470

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0469

<1:1.8.0.45-30.b13.5.amzn1
  • H
CVE-2015-0408

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2015-0410

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2015-0407

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2015-0437

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6587

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2015-0395

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2015-0412

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6591

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2015-0383

<1:1.8.0.31-2.b13.5.amzn1
  • H
Cryptographic Issues

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6601

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6585

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6549

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6593

<1:1.8.0.31-2.b13.5.amzn1
  • H
CVE-2014-6562

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6519

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6531

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6558

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6512

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6517

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6511

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6504

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6468

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6506

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6457

<1:1.8.0.25-0.b18.4.amzn1
  • H
CVE-2014-6502

<1:1.8.0.25-0.b18.4.amzn1