Homepage

java-1.7.0-openjdk-headless vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.7.0-openjdk-headless 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
Integer Overflow or Wraparound

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Access Control

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Integer Coercion Error

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Incorrect Behavior Order: Early Validation

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Resource Leak

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Use of Validation Framework

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Integer Underflow

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Input Validation

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Use of Validation Framework

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Authorization

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Allocation of Resources Without Limits or Throttling

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Resource Exhaustion

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Cross-boundary Removal of Sensitive Data

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Improper Use of Validation Framework

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Integer Overflow or Wraparound

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

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • H
Uncaught Exception

<1:1.7.0.321-2.6.28.2.amzn2.0.1
  • C
Deserialization of Untrusted Data

<1:1.7.0.261-2.6.22.2.amzn2.0.2
  • C
Deserialization of Untrusted Data

<1:1.7.0.261-2.6.22.2.amzn2.0.2
  • H
CVE-2020-2800

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
CVE-2020-2805

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
CVE-2020-2830

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
CVE-2020-2773

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
CVE-2020-2803

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
CVE-2020-2781

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.7.0.261-2.6.22.2.amzn2.0.1
  • H
CVE-2020-2659

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • H
Deserialization of Untrusted Data

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • H
CVE-2020-2601

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • H
CVE-2020-2654

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • H
CVE-2020-2593

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • H
Improper Handling of Exceptional Conditions

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • H
CVE-2020-2590

<1:1.7.0.251-2.6.21.0.amzn2.0.1
  • M
CVE-2019-2999

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2992

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2989

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2988

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2987

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2983

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2964

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2981

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

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2973

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

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2962

<1:1.7.0.241-2.6.20.0.amzn2.0.2
  • M
CVE-2019-2816

<1:1.7.0.231-2.6.19.1.amzn2.0.1
  • M
CVE-2019-2842

<1:1.7.0.231-2.6.19.1.amzn2.0.1
  • M
CVE-2019-2762

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

<1:1.7.0.231-2.6.19.1.amzn2.0.1
  • M
CVE-2019-2769

<1:1.7.0.231-2.6.19.1.amzn2.0.1
  • M
CVE-2019-2745

<1:1.7.0.231-2.6.19.1.amzn2.0.1
  • H
CVE-2019-2698

<1:1.7.0.221-2.6.18.1.amzn2.0.1
  • H
CVE-2019-2684

<1:1.7.0.221-2.6.18.1.amzn2.0.1
  • H
Resource Exhaustion

<1:1.7.0.221-2.6.18.1.amzn2.0.1
  • M
CVE-2019-2422

<1:1.7.0.211-2.6.17.1.amzn2.0.1
  • C
CVE-2018-3214

<1:1.7.0.201-2.6.16.1.amzn2.0.1
  • C
CVE-2018-3180

<1:1.7.0.201-2.6.16.1.amzn2.0.1
  • C
CVE-2018-3149

<1:1.7.0.201-2.6.16.1.amzn2.0.1
  • C
CVE-2018-3139

<1:1.7.0.201-2.6.16.1.amzn2.0.1
  • C
CVE-2018-3169

<1:1.7.0.201-2.6.16.1.amzn2.0.1
  • C
CVE-2018-3136

<1:1.7.0.201-2.6.16.1.amzn2.0.1
  • M
CVE-2018-2952

<1:1.7.0.191-2.6.15.4.amzn2
  • H
Information Exposure

<1:1.7.0.181-2.6.14.8.amzn2
  • C
CVE-2018-2799

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2815

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2800

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2798

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2794

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2795

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2814

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2790

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2797

<1:1.7.0.181-2.6.14.5.amzn2
  • C
CVE-2018-2796

<1:1.7.0.181-2.6.14.5.amzn2