Homepage

java-1.8.0-openjdk-debug vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.8.0-openjdk-debug 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
Uncontrolled Memory Allocation

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
Out-of-bounds Read

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
Improper Input Validation

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
CVE-2024-21140

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
CVE-2024-21131

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
Signed to Unsigned Conversion Error

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
Integer Overflow or Wraparound

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
Improper Handling of Length Parameter Inconsistency

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
CVE-2024-21147

<1:1.8.0.432.b06-1.amzn2.0.1
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.8.0.432.b06-1.amzn2.0.1
  • L
Uncontrolled Memory Allocation

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
Out-of-bounds Write

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
Integer Overflow or Wraparound

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
Improper Output Neutralization for Logs

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
CVE-2024-21005

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
CVE-2024-21003

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
CVE-2024-21004

<1:1.8.0.412.b08-1.amzn2.0.1
  • L
CVE-2024-21002

<1:1.8.0.412.b08-1.amzn2.0.1
  • H
Information Exposure Through Log Files

<1:1.8.0.402.b06-1.amzn2.0.1
  • H
Improper Input Validation

<1:1.8.0.402.b06-1.amzn2.0.1
  • H
Integer Overflow or Wraparound

<1:1.8.0.402.b06-1.amzn2.0.1
  • H
Covert Timing Channel

<1:1.8.0.402.b06-1.amzn2.0.1
  • H
Improper Input Validation

<1:1.8.0.402.b06-1.amzn2.0.1
  • H
Improper Input Validation

<1:1.8.0.402.b06-1.amzn2.0.1
  • M
Improper Certificate Validation

<1:1.8.0.392.b08-2.amzn2.0.1
  • M
Deserialization of Untrusted Data

<1:1.8.0.392.b08-2.amzn2.0.1
  • H
Resource Exhaustion

<1:1.8.0.382.b05-1.amzn2.0.2
  • M
CVE-2023-22043

<1:1.8.0.382.b05-1.amzn2.0.1
  • M
Out-of-bounds Read

<1:1.8.0.382.b05-1.amzn2.0.1
  • H
Improper Input Validation

<1:1.8.0.372.b07-1.amzn2.0.1
  • H
Improperly Implemented Security Check for Standard

<1:1.8.0.372.b07-1.amzn2.0.1
  • H
Improper Input Validation

<1:1.8.0.372.b07-1.amzn2.0.1
  • H
Improper Neutralization of Null Byte or NUL Character

<1:1.8.0.372.b07-1.amzn2.0.1
  • H
Improper Neutralization of Null Byte or NUL Character

<1:1.8.0.372.b07-1.amzn2.0.1
  • H
Information Exposure

<1:1.8.0.372.b07-1.amzn2.0.1
  • H
Improper Enforcement of Message Integrity During Transmission in a Communication Channel

<1:1.8.0.372.b07-1.amzn2.0.1
  • M
Deserialization of Untrusted Data

<1:1.8.0.362.b08-1.amzn2.0.1
  • M
Allocation of Resources Without Limits or Throttling

<1:1.8.0.352.b08-2.amzn2.0.1
  • M
Resource Exhaustion

<1:1.8.0.352.b08-2.amzn2.0.1
  • M
Integer Coercion Error

<1:1.8.0.352.b08-2.amzn2.0.1
  • M
Use of Insufficiently Random Values

<1:1.8.0.352.b08-2.amzn2.0.1
  • H
Integer Coercion Error

<1:1.8.0.342.b07-1.amzn2.0.1
  • H
Improper Access Control

<1:1.8.0.342.b07-1.amzn2.0.1
  • H
Resource Leak

<1:1.8.0.342.b07-1.amzn2.0.1
  • M
Allocation of Resources Without Limits or Throttling

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Integer Overflow or Wraparound

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Improper Use of Validation Framework

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Allocation of Resources Without Limits or Throttling

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Integer Overflow or Wraparound

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Improper Authorization

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Allocation of Resources Without Limits or Throttling

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Improper Use of Validation Framework

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Uncaught Exception

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Improper Cross-boundary Removal of Sensitive Data

<1:1.8.0.332.b09-1.amzn2.0.2
  • M
Deserialization of Untrusted Data

<1:1.8.0.332.b09-1.amzn2.0.2
  • C
Deserialization of Untrusted Data

<1:1.8.0.312.b07-1.amzn2.0.2
  • C
Deserialization of Untrusted Data

<1:1.8.0.312.b07-1.amzn2.0.2
  • H
CVE-2021-35603

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35588

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35586

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35578

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35567

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35565

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35564

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35561

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
Incorrect Authorization

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-35556

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
Incorrect Authorization

<1:1.8.0.312.b07-1.amzn2.0.1
  • H
CVE-2021-2388

<1:1.8.0.302.b08-0.amzn2.0.1
  • H
CVE-2021-2369

<1:1.8.0.302.b08-0.amzn2.0.1
  • H
CVE-2021-2341

<1:1.8.0.302.b08-0.amzn2.0.1
  • M
CVE-2020-14803

<1:1.8.0.272.b10-1.amzn2.0.1
  • M
CVE-2020-14796

<1:1.8.0.272.b10-1.amzn2.0.1
  • M
CVE-2020-14797

<1:1.8.0.272.b10-1.amzn2.0.1
  • M
CVE-2020-14792

<1:1.8.0.272.b10-1.amzn2.0.1
  • M
CVE-2020-14781

<1:1.8.0.272.b10-1.amzn2.0.1
  • M
CVE-2020-14782

<1:1.8.0.272.b10-1.amzn2.0.1
  • M
CVE-2020-14779

<1:1.8.0.272.b10-1.amzn2.0.1
  • H
CVE-2020-14621

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-14583

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-14593

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-14579

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-14577

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-14578

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-14556

<1:1.8.0.265.b01-1.amzn2.0.1
  • H
CVE-2020-2830

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2805

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2800

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2781

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2803

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2773

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2754

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2755

<1:1.8.0.252.b09-2.amzn2.0.1
  • H
CVE-2020-2659

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
CVE-2020-2654

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
CVE-2020-2601

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
CVE-2020-2593

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
CVE-2020-2590

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
Improper Handling of Exceptional Conditions

<1:1.8.0.242.b08-0.amzn2.0.1
  • H
CVE-2019-2842

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2816

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2786

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2769

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2762

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2745

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2698

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
CVE-2019-2684

<1:1.8.0.222.b10-0.amzn2.0.1
  • H
Resource Exhaustion

<1:1.8.0.222.b10-0.amzn2.0.1
  • M
CVE-2019-2422

<1:1.8.0.201.b09-0.amzn2
  • C
CVE-2018-3214

<1:1.8.0.191.b12-0.amzn2
  • C
CVE-2018-3180

<1:1.8.0.191.b12-0.amzn2
  • C
CVE-2018-3183

<1:1.8.0.191.b12-0.amzn2
  • C
CVE-2018-3169

<1:1.8.0.191.b12-0.amzn2
  • C
CVE-2018-3149

<1:1.8.0.191.b12-0.amzn2
  • C
CVE-2018-3139

<1:1.8.0.191.b12-0.amzn2
  • C
CVE-2018-3136

<1:1.8.0.191.b12-0.amzn2
  • M
CVE-2018-2952

<1:1.8.0.181-3.b13.amzn2
  • H
Information Exposure

<1:1.8.0.171-8.b10.amzn2
  • C
CVE-2018-2815

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

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

<1:1.8.0.171-7.b10.amzn2
  • C
CVE-2018-2800

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<1:1.8.0.161-0.b14.amzn2