dotnet-host

Direct Vulnerabilities

Known vulnerabilities in the dotnet-host package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • H
Resource Exhaustion

<0:10.0.9-1.0.1.el8_10
  • H
Link Following

<0:10.0.9-1.0.1.el8_10
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<0:10.0.8-1.0.1.el8_10
  • H
Improper Input Validation

<0:10.0.6-1.0.1.el8_10
  • H
Resource Exhaustion

<0:10.0.6-1.0.1.el8_10
  • H
Improper Neutralization of Special Elements

<0:10.0.6-1.0.1.el8_10
  • H
Improper Input Validation

<0:10.0.6-1.0.1.el8_10
  • H
Allocation of Resources Without Limits or Throttling

<0:10.0.4-1.0.1.el8_10
  • H
Out-of-bounds Read

<0:10.0.4-1.0.1.el8_10
  • H
Inadequate Encryption Strength

<0:9.0.10-1.0.1.el8_10
  • H
Link Following

<0:9.0.10-1.0.1.el8_10
  • H
HTTP Request Smuggling

<0:9.0.10-1.0.1.el8_10
  • H
Untrusted Search Path

<0:9.0.6-1.0.1.el8_10
  • H
External Control of File Name or Path

<0:9.0.5-1.0.1.el8_10
  • H
CVE-2025-24070

<0:9.0.3-1.0.1.el8_10
  • H
CVE-2025-21172

<0:9.0.1-1.0.1.el8_10
  • H
Buffer Over-read

<0:9.0.1-1.0.1.el8_10
  • H
CVE-2025-21173

<0:9.0.1-1.0.1.el8_10
  • H
Heap-based Buffer Overflow

<0:9.0.1-1.0.1.el8_10
  • H
CVE-2024-43483

<0:8.0.10-1.0.1.el8_10
  • H
CVE-2024-38229

<0:8.0.10-1.0.1.el8_10
  • H
CVE-2024-43485

<0:8.0.10-1.0.1.el8_10
  • H
CVE-2024-43484

<0:8.0.10-1.0.1.el8_10
  • M
CVE-2024-38167

<0:8.0.8-1.0.1.el8_10
  • H
CVE-2024-35264

<0:8.0.7-1.0.1.el8_10
  • H
CVE-2024-30105

<0:8.0.7-1.0.1.el8_10
  • H
CVE-2024-38095

<0:8.0.7-1.0.1.el8_10
  • H
Race Condition

<0:8.0.5-1.0.1.el8_10
  • H
CVE-2024-30045

<0:8.0.5-1.0.1.el8_10
  • M
CVE-2024-21392

<0:8.0.3-1.0.1.el8_9
  • H
CVE-2024-21386

<0:8.0.2-2.0.1.el8_9
  • H
CVE-2024-21404

<0:8.0.2-2.0.1.el8_9
  • H
CVE-2024-21319

<0:8.0.1-1.0.1.el8_9
  • H
CVE-2024-0056

<0:8.0.1-1.0.1.el8_9
  • H
CVE-2024-0057

<0:8.0.1-1.0.1.el8_9
  • M
CVE-2023-36558

<0:7.0.14-1.0.1.el8_9
  • M
CVE-2023-36049

<0:7.0.14-1.0.1.el8_9
  • H
CVE-2023-44487

<0:7.0.12-1.0.1.el8_8
  • M
CVE-2023-36799

<0:7.0.13-1.0.1.el8_8
  • H
CVE-2023-35390

<0:7.0.10-1.0.1.el8_8
  • H
CVE-2023-38180

<0:7.0.10-1.0.1.el8_8
  • H
Race Condition

<0:7.0.9-1.0.1.el8_8
  • H
CVE-2023-32032

<0:7.0.7-1.0.1.el8_8
  • H
CVE-2023-33128

<0:7.0.7-1.0.1.el8_8
  • H
CVE-2023-29331

<0:7.0.7-1.0.1.el8_8
  • H
CVE-2023-29337

<0:7.0.7-1.0.1.el8_8
  • H
CVE-2023-24936

<0:7.0.7-1.0.1.el8_8
  • M
CVE-2022-41032

<0:7.0.0-0.4.rc2.0.1.el8_7
  • M
CVE-2022-38013

<0:6.0.9-1.0.1.el8_6
  • M
CVE-2022-34716

<0:6.0.8-1.0.1.el8_6
  • M
CVE-2022-30184

<0:6.0.6-1.0.1.el8_6
  • H
CVE-2022-23267

<0:6.0.5-1.0.1.el8_6
  • H
CVE-2022-29145

<0:6.0.5-1.0.1.el8_6
  • H
CVE-2022-29117

<0:6.0.5-1.0.1.el8_6
  • H
CVE-2022-24464

<0:6.0.3-4.0.1.el8_5
  • H
CVE-2022-24512

<0:6.0.3-4.0.1.el8_5
  • H
CVE-2022-21986

<0:6.0.2-1.0.1.el8_5
  • H
CVE-2021-41355

<0:5.0.11-1.0.1.el8_4
  • H
CVE-2021-34485

<0:5.0.9-1.0.1.el8_4
  • H
CVE-2021-26423

<0:5.0.9-1.0.1.el8_4
  • H
CVE-2021-34532

<0:5.0.9-1.0.1.el8_4
  • H
CVE-2021-31957

<0:5.0.7-1.0.1.el8_4
  • H
CVE-2021-31204

<0:5.0.6-1.0.1.el8_4
  • H
CVE-2021-26701

<0:5.0.4-1.0.1.el8_3
  • H
CVE-2021-1721

<0:5.0.3-1.0.1.el8_3
  • H
CVE-2021-1723

<0:5.0.2-2.0.1.el8_3
  • H
CVE-2020-1045

<0:3.1.8-2.0.1.el8_2
  • H
CVE-2020-1597

<0:3.1.7-1.0.1.el8_2
  • C
CVE-2020-1147

<0:3.1.6-1.0.1.el8_2
  • H
CVE-2020-1161

<0:3.1.4-2.0.2.el8_2
  • H
CVE-2020-1108

<0:3.1.5-2.0.1.el8_2
  • C
Out-of-bounds Write

<0:3.0.2-2.0.1.el8_1
  • C
CVE-2020-0602

<0:3.0.2-2.0.1.el8_1
  • M
CVE-2019-1301

<0:2.1.13-1.el8_0
  • H
Resource Exhaustion

<0:2.1.11-2.el8_0
  • H
Improper Data Handling

<0:2.1.11-2.el8_0
  • H
CVE-2019-0757

<0:2.1.11-2.el8_0
  • H
Improper Data Handling

<0:2.1.11-2.el8_0