Homepage

xen-libs vulnerabilities

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the xen-libs 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-45819

<4.14.6_22-150300.3.84.1
  • H
CVE-2024-45818

<4.14.6_22-150300.3.84.1
  • L
CVE-2024-31146

<4.14.6_18-150300.3.78.1
  • H
CVE-2024-31145

<4.14.6_18-150300.3.78.1
  • H
CVE-2024-31143

<4.14.6_16-150300.3.75.1
  • M
CVE-2024-2201

<4.14.6_16-150300.3.75.1
  • M
CVE-2023-46839

<4.14.6_10-150300.3.63.1
  • M
CVE-2023-46836

<4.14.6_08-150300.3.60.1
  • M
CVE-2023-46835

<4.14.6_08-150300.3.60.1
  • M
CVE-2023-34328

<4.14.6_06-150300.3.57.1
  • M
CVE-2023-34327

<4.14.6_06-150300.3.57.1
  • H
CVE-2023-34326

<4.14.6_06-150300.3.57.1
  • M
Out-of-bounds Write

<4.14.6_06-150300.3.57.1
  • M
NULL Pointer Dereference

<4.14.6_06-150300.3.57.1
  • H
Improper Check for Dropped Privileges

<4.14.6_04-150300.3.54.1
  • M
CVE-2023-20593

<4.14.6_04-150300.3.54.1
  • M
Divide By Zero

<4.14.6_04-150300.3.54.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_12-150300.3.48.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_12-150300.3.48.1
  • H
Use After Free

<4.14.5_12-150300.3.48.1
  • M
CVE-2022-42331

<4.14.5_12-150300.3.48.1
  • M
CVE-2022-23824

<4.14.5_10-150300.3.45.1
  • M
Memory Leak

<4.14.5_08-150300.3.40.1
  • M
Memory Leak

<4.14.5_08-150300.3.40.1
  • M
Memory Leak

<4.14.5_08-150300.3.40.1
  • M
Memory Leak

<4.14.5_08-150300.3.40.1
  • M
Uncontrolled Recursion

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Memory Leak

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • H
Incomplete Cleanup

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.5_08-150300.3.40.1
  • M
Incomplete Cleanup

<4.14.5_08-150300.3.40.1
  • M
Improper Handling of Exceptional Conditions

<4.14.5_08-150300.3.40.1
  • L
Improper Resource Shutdown or Release

<4.14.5_08-150300.3.40.1
  • H
Release of Invalid Pointer or Reference

<4.14.5_08-150300.3.40.1
  • M
Improper Resource Shutdown or Release

<4.14.5_08-150300.3.40.1
  • M
Improper Handling of Exceptional Conditions

<4.14.5_06-150300.3.35.1
  • M
Improper Resource Shutdown or Release

<4.14.5_06-150300.3.35.1
  • H
CVE-2022-33745

<4.14.5_06-150300.3.35.1
  • M
Information Exposure

<4.14.5_06-150300.3.35.1
  • M
Information Exposure

<4.14.5_06-150300.3.35.1
  • M
Improper Cross-boundary Removal of Sensitive Data

<4.14.5_06-150300.3.35.1
  • M
Memory Leak

<4.14.5_06-150300.3.35.1
  • M
Improper Cross-boundary Removal of Sensitive Data

<4.14.5_06-150300.3.35.1
  • H
CVE-2022-33745

<4.14.5_04-150300.3.32.1
  • M
Improper Cross-boundary Removal of Sensitive Data

<4.14.5_04-150300.3.32.1
  • H
CVE-2022-26364

<4.14.5_04-150300.3.32.1
  • H
CVE-2022-26363

<4.14.5_04-150300.3.32.1
  • H
Race Condition

<4.14.5_04-150300.3.32.1
  • M
Exposure of Resource to Wrong Sphere

<4.14.5_04-150300.3.32.1
  • M
CVE-2022-23816

<4.14.5_04-150300.3.32.1
  • M
Incomplete Cleanup

<4.14.5_04-150300.3.32.1
  • M
Incomplete Cleanup

<4.14.5_04-150300.3.32.1
  • M
Incomplete Cleanup

<4.14.5_04-150300.3.32.1
  • H
CVE-2022-26364

<4.14.5_02-150300.3.29.1
  • H
CVE-2022-26363

<4.14.5_02-150300.3.29.1
  • H
Race Condition

<4.14.5_02-150300.3.29.1
  • M
CVE-2022-26360

<4.14.5_02-150300.3.29.1
  • M
CVE-2022-26361

<4.14.5_02-150300.3.29.1
  • M
CVE-2022-26359

<4.14.5_02-150300.3.29.1
  • M
CVE-2022-26358

<4.14.5_02-150300.3.29.1
  • M
CVE-2022-26361

<4.14.4_04-150300.3.24.1
  • M
CVE-2022-26360

<4.14.4_04-150300.3.24.1
  • M
CVE-2022-26359

<4.14.4_04-150300.3.24.1
  • M
CVE-2022-26358

<4.14.4_04-150300.3.24.1
  • M
Race Condition

<4.14.4_04-150300.3.24.1
  • M
Improper Locking

<4.14.4_04-150300.3.24.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.2_04-3.9.1
  • H
CVE-2021-28695

<4.14.2_04-3.9.1
  • H
Incorrect Authorization

<4.14.2_04-3.9.1
  • M
CVE-2021-28699

<4.14.2_04-3.9.1
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<4.14.2_04-3.9.1
  • H
CVE-2021-28694

<4.14.2_04-3.9.1
  • H
Race Condition

<4.14.2_04-3.9.1
  • M
CVE-2021-28693

<4.14.2_04-3.9.1
  • M
CVE-2021-28690

<4.14.2_04-3.9.1
  • M
Improper Privilege Management

<4.14.2_04-3.9.1
  • M
Information Exposure

<4.14.2_04-3.9.1
  • H
Race Condition

<4.14.2_06-3.12.1
  • M
Improper Handling of Exceptional Conditions

<4.14.3_04-3.15.1
  • M
CVE-2021-28708

<4.14.3_04-3.15.1
  • M
CVE-2021-28707

<4.14.3_04-3.15.1
  • M
Improper Privilege Management

<4.14.3_04-3.15.1
  • M
CVE-2021-28704

<4.14.3_04-3.15.1
  • M
Improper Handling of Exceptional Conditions

<4.14.3_04-3.15.1
  • M
Allocation of Resources Without Limits or Throttling

<4.14.3_04-3.15.1
  • M
Incomplete Cleanup

<4.14.3_06-150300.3.18.2
  • L
Integer Underflow

<4.14.3_06-150300.3.18.2
  • H
Improper Resource Shutdown or Release

<4.14.3_06-150300.3.18.2
  • M
CVE-2021-26401

<4.14.4_02-150300.3.21.1
  • M
CVE-2022-0001

<4.14.4_02-150300.3.21.1
  • M
CVE-2022-0002

<4.14.4_02-150300.3.21.1