java-1_8_0-ibm-plugin vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the java-1_8_0-ibm-plugin 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
CVE-2024-3933

<1.8.0_sr8.35-150000.3.95.1
  • M
CVE-2024-21235

<1.8.0_sr8.35-150000.3.95.1
  • M
CVE-2024-21217

<1.8.0_sr8.35-150000.3.95.1
  • M
CVE-2024-21210

<1.8.0_sr8.35-150000.3.95.1
  • M
CVE-2024-21208

<1.8.0_sr8.35-150000.3.95.1
  • M
CVE-2024-27267

<1.8.0_sr8.30-150000.3.92.1
  • H
CVE-2024-21147

<1.8.0_sr8.30-150000.3.92.1
  • M
CVE-2024-21145

<1.8.0_sr8.30-150000.3.92.1
  • L
CVE-2024-21144

<1.8.0_sr8.30-150000.3.92.1
  • M
CVE-2024-21140

<1.8.0_sr8.30-150000.3.92.1
  • L
CVE-2024-21138

<1.8.0_sr8.30-150000.3.92.1
  • L
CVE-2024-21131

<1.8.0_sr8.30-150000.3.92.1
  • L
CVE-2024-21085

<1.8.0_sr8.25-150000.3.89.1
  • L
CVE-2024-21011

<1.8.0_sr8.25-150000.3.89.1
  • M
Deserialization of Untrusted Data

<1.8.0_sr8.25-150000.3.89.1
  • L
CVE-2024-21094

<1.8.0_sr8.25-150000.3.89.1
  • L
CVE-2024-21068

<1.8.0_sr8.25-150000.3.89.1
  • L
CVE-2024-21012

<1.8.0_sr8.25-150000.3.89.1
  • H
CVE-2024-20952

<1.8.0_sr8.20-150000.3.86.1
  • M
CVE-2024-20945

<1.8.0_sr8.20-150000.3.86.1
  • H
CVE-2024-20932

<1.8.0_sr8.20-150000.3.86.1
  • M
CVE-2024-20926

<1.8.0_sr8.20-150000.3.86.1
  • M
CVE-2024-20921

<1.8.0_sr8.20-150000.3.86.1
  • M
CVE-2024-20919

<1.8.0_sr8.20-150000.3.86.1
  • H
CVE-2024-20918

<1.8.0_sr8.20-150000.3.86.1
  • H
Information Exposure

<1.8.0_sr8.20-150000.3.86.1
  • M
Race Condition

<1.8.0_sr8.15-150000.3.83.1
  • M
CVE-2023-22081

<1.8.0_sr8.15-150000.3.83.1
  • M
CVE-2023-22067

<1.8.0_sr8.15-150000.3.83.1
  • L
CVE-2023-22025

<1.8.0_sr8.15-150000.3.83.1
  • L
CVE-2023-22049

<1.8.0_sr8.10-150000.3.80.1
  • H
Allocation of Resources Without Limits or Throttling

<1.8.0_sr8.10-150000.3.80.1
  • L
CVE-2023-22045

<1.8.0_sr8.10-150000.3.80.1
  • L
CVE-2023-22044

<1.8.0_sr8.10-150000.3.80.1
  • M
CVE-2023-22041

<1.8.0_sr8.10-150000.3.80.1
  • L
CVE-2023-22036

<1.8.0_sr8.10-150000.3.80.1
  • L
CVE-2023-22006

<1.8.0_sr8.10-150000.3.80.1
  • H
Deserialization of Untrusted Data

<1.8.0_sr8.10-150000.3.80.1
  • L
SUSE-SU-2023:2862-1

<1.8.0_sr8.6-150000.3.77.1
  • H
CVE-2023-30441

<1.8.0_sr8.5-150000.3.74.1
  • M
Out-of-bounds Read

<1.8.0_sr8.5-150000.3.74.1
  • L
CVE-2023-21968

<1.8.0_sr8.5-150000.3.74.1
  • M
CVE-2023-21967

<1.8.0_sr8.5-150000.3.74.1
  • M
CVE-2023-21954

<1.8.0_sr8.5-150000.3.74.1
  • M
CVE-2023-21939

<1.8.0_sr8.5-150000.3.74.1
  • L
CVE-2023-21938

<1.8.0_sr8.5-150000.3.74.1
  • L
CVE-2023-21937

<1.8.0_sr8.5-150000.3.74.1
  • H
CVE-2023-21930

<1.8.0_sr8.5-150000.3.74.1
  • L
CVE-2023-21843

<1.8.0_sr8.0-150000.3.71.1
  • M
CVE-2023-21835

<1.8.0_sr8.0-150000.3.71.1
  • M
CVE-2023-21830

<1.8.0_sr8.0-150000.3.71.1
  • M
CVE-2022-21426

<1.8.0_sr8.0-150000.3.71.1
  • M
Access of Resource Using Incompatible Type ('Type Confusion')

<1.8.0_sr7.20-150000.3.68.1
  • 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
  • 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