Homepage

java-1_8_0-ibm vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1_8_0-ibm 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
  • L
CVE-2022-39399

<1.8.0_sr7.20-150000.3.65.1
  • H
Incorrect Conversion between Numeric Types

<1.8.0_sr7.20-150000.3.65.1
  • M
CVE-2022-21628

<1.8.0_sr7.20-150000.3.65.1
  • M
CVE-2022-21626

<1.8.0_sr7.20-150000.3.65.1
  • L
CVE-2022-21624

<1.8.0_sr7.20-150000.3.65.1
  • L
CVE-2022-21619

<1.8.0_sr7.20-150000.3.65.1
  • M
CVE-2022-21618

<1.8.0_sr7.20-150000.3.65.1
  • M
CVE-2022-21549

<1.8.0_sr7.20-150000.3.65.1
  • M
CVE-2022-21541

<1.8.0_sr7.20-150000.3.65.1
  • M
CVE-2022-21540

<1.8.0_sr7.20-150000.3.65.1
  • H
Incorrect Conversion between Numeric Types

<1.8.0_sr7.11-150000.3.62.1
  • M
CVE-2022-21549

<1.8.0_sr7.11-150000.3.62.1
  • M
CVE-2022-21541

<1.8.0_sr7.11-150000.3.62.1
  • M
CVE-2022-21540

<1.8.0_sr7.11-150000.3.62.1
  • H
CVE-2022-21476

<1.8.0_sr7.10-150000.3.59.1
  • M
CVE-2022-21496

<1.8.0_sr7.10-150000.3.59.1
  • H
CVE-2022-21449

<1.8.0_sr7.10-150000.3.59.1
  • L
CVE-2022-21443

<1.8.0_sr7.10-150000.3.59.1
  • M
CVE-2022-21434

<1.8.0_sr7.10-150000.3.59.1
  • M
CVE-2022-21426

<1.8.0_sr7.10-150000.3.59.1
  • M
CVE-2022-21299

<1.8.0_sr7.10-150000.3.59.1
  • M
CVE-2021-35561

<1.8.0_sr7.10-150000.3.59.1
  • M
CVE-2018-2796

<1.8.0_sr5.15-3.3.4
  • H
CVE-2018-2783

<1.8.0_sr5.15-3.3.4
  • M
CVE-2018-2794

<1.8.0_sr5.15-3.3.4
  • H
CVE-2018-2797

<1.8.0_sr5.15-3.3.4
  • M
CVE-2018-2799

<1.8.0_sr5.15-3.3.4
  • M
CVE-2018-2795

<1.8.0_sr5.15-3.3.4
  • M
CVE-2018-2800

<1.8.0_sr5.15-3.3.4
  • M
CVE-2018-2798

<1.8.0_sr5.15-3.3.4
  • H
CVE-2018-2826

<1.8.0_sr5.15-3.3.4
  • H
CVE-2018-2814

<1.8.0_sr5.15-3.3.4
  • H
Incorrect Permission Assignment for Critical Resource

<1.8.0_sr5.15-3.3.4
  • H
CVE-2018-2825

<1.8.0_sr5.15-3.3.4
  • L
CVE-2018-2790

<1.8.0_sr5.15-3.3.4
  • H
CVE-2018-2952

<1.8.0_sr5.20-3.6.2
  • L
Information Exposure

<1.8.0_sr5.20-3.6.2
  • H
CVE-2018-3169

<1.8.0_sr5.25-3.9.1
  • L
CVE-2018-3136

<1.8.0_sr5.25-3.9.1
  • H
CVE-2018-3149

<1.8.0_sr5.25-3.9.1
  • H
CVE-2018-2973

<1.8.0_sr5.20-3.6.2
  • H
Deserialization of Untrusted Data

<1.8.0_sr5.20-3.6.2
  • H
CVE-2018-2940

<1.8.0_sr5.20-3.6.2
  • C
CVE-2016-0705

<1.8.0_sr5.20-3.6.2
  • C
Improper Input Validation

<1.8.0_sr5.20-3.6.2
  • C
Directory Traversal

<1.8.0_sr5.20-3.6.2
  • H
CVE-2018-2964

<1.8.0_sr5.20-3.6.2
  • M
Information Exposure

<1.8.0_sr5.20-3.6.2
  • M
CVE-2018-3214

<1.8.0_sr5.25-3.9.1
  • C
CVE-2018-3183

<1.8.0_sr5.25-3.9.1
  • M
CVE-2018-3180

<1.8.0_sr5.25-3.9.1
  • L
Integer Overflow or Wraparound

<1.8.0_sr5.25-3.9.1
  • L
CVE-2018-3139

<1.8.0_sr5.25-3.9.1
  • M
Uncontrolled Search Path Element

<1.8.0_sr5.30-3.16.2
  • L
CVE-2019-2422

<1.8.0_sr5.30-3.16.2
  • L
Divide By Zero

<1.8.0_sr5.30-3.16.2
  • L
CVE-2019-2449

<1.8.0_sr5.30-3.16.2
  • L
CVE-2019-2697

<1.8.0_sr5.35-3.20.1
  • M
Out-of-Bounds

<1.8.0_sr5.35-3.20.1
  • M
CVE-2019-2684

<1.8.0_sr5.35-3.20.1
  • L
CVE-2019-2698

<1.8.0_sr5.35-3.20.1
  • M
Resource Exhaustion

<1.8.0_sr5.35-3.20.1
  • H
Uncontrolled Search Path Element

<1.8.0_sr5.40-3.24.1
  • L
Use After Free

<1.8.0_sr5.40-3.24.1
  • M
CVE-2019-2816

<1.8.0_sr5.40-3.24.1
  • L
CVE-2019-2786

<1.8.0_sr5.40-3.24.1
  • M
CVE-2019-2769

<1.8.0_sr5.40-3.24.1
  • L
CVE-2019-2766

<1.8.0_sr5.40-3.24.1
  • M
CVE-2019-2762

<1.8.0_sr5.40-3.24.1
  • L
CVE-2019-2449

<1.8.0_sr5.40-3.24.1
  • H
Time-of-check Time-of-use (TOCTOU)

<1.8.0_sr5.40-3.24.1
  • H
Out-of-bounds Write

<1.8.0_sr5.40-3.24.1
  • H
Access Restriction Bypass

<1.8.0_sr5.40-3.24.1
  • L
Divide By Zero

<1.8.0_sr5.40-3.24.1
  • M
CVE-2019-2999

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2996

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2981

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2992

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2989

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2988

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2983

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2978

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2975

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2973

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2964

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2958

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2945

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2962

<1.8.0_sr6.0-3.30.1
  • M
CVE-2019-2933

<1.8.0_sr6.0-3.30.1
  • C
Improper Privilege Management

<1.8.0_sr6.0-3.30.1
  • L
CVE-2020-2659

<1.8.0_sr6.5-3.33.2
  • H
Deserialization of Untrusted Data

<1.8.0_sr6.5-3.33.2
  • M
CVE-2020-2593

<1.8.0_sr6.5-3.33.2
  • M
Improper Handling of Exceptional Conditions

<1.8.0_sr6.5-3.33.2
  • M
Untrusted Search Path

<1.8.0_sr6.5-3.33.2
  • H
CVE-2020-2755

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-2830

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-2803

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-2781

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-2805

<1.8.0_sr6.10-3.38.1
  • H
Deserialization of Untrusted Data

<1.8.0_sr6.10-3.38.1
  • H
Deserialization of Untrusted Data

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-2800

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-2754

<1.8.0_sr6.10-3.38.1
  • M
CVE-2019-2949

<1.8.0_sr6.10-3.38.1
  • M
CVE-2020-2654

<1.8.0_sr6.10-3.38.1
  • H
CVE-2020-14593

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14621

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14583

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14581

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14578

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14577

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14556

<1.8.0_sr6.15-3.41.1
  • M
Access of Resource Using Incompatible Type ('Type Confusion')

<1.8.0_sr6.15-3.41.1
  • H
CVE-2020-14579

<1.8.0_sr6.15-3.41.1
  • M
CVE-2020-14803

<1.8.0_sr6.20-3.47.1
  • M
CVE-2020-14797

<1.8.0_sr6.20-3.47.1
  • M
CVE-2020-14798

<1.8.0_sr6.20-3.47.1
  • M
CVE-2020-14796

<1.8.0_sr6.20-3.47.1
  • M
CVE-2020-14781

<1.8.0_sr6.20-3.47.1
  • M
CVE-2020-14792

<1.8.0_sr6.20-3.47.1
  • M
CVE-2020-14779

<1.8.0_sr6.20-3.47.1
  • C
Out-of-bounds Write

<1.8.0_sr6.25-3.50.1
  • M
CVE-2020-14803

<1.8.0_sr6.25-3.50.1
  • L
CVE-2021-41035

<1.8.0_sr7.0-3.53.1
  • L
CVE-2021-35588

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-35586

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-35578

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-35565

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-35564

<1.8.0_sr7.0-3.53.1
  • H
CVE-2021-35560

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-35559

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-35556

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-2369

<1.8.0_sr7.0-3.53.1
  • L
CVE-2021-2341

<1.8.0_sr7.0-3.53.1
  • M
CVE-2021-2163

<1.8.0_sr7.0-3.53.1
  • M
CVE-2022-21366

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21365

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21360

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21349

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21341

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21340

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21305

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21299

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21296

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21294

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21293

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21291

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21283

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21282

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21277

<1.8.0_sr7.5-150000.3.56.1
  • M
CVE-2022-21271

<1.8.0_sr7.5-150000.3.56.1
  • L
CVE-2022-21248

<1.8.0_sr7.5-150000.3.56.1