Homepage

dotnet-host

Report a new vulnerability Found a mistake?

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
  • C
Link Following

<0:10.0.13-1.0.1.el9_8
  • C
Out-of-bounds Write

<0:10.0.13-1.0.1.el9_8
  • C
Information Exposure

<0:10.0.13-1.0.1.el9_8
  • C
Improperly Controlled Sequential Memory Allocation

<0:10.0.13-1.0.1.el9_8
  • C
Origin Validation Error

<0:10.0.13-1.0.1.el9_8
  • C
Allocation of Resources Without Limits or Throttling

<0:10.0.13-1.0.1.el9_8
  • C
Arbitrary Code Injection

<0:10.0.13-1.0.1.el9_8
  • C
Uncontrolled Recursion

<0:10.0.13-1.0.1.el9_8
  • C
HTTP Request Smuggling

<0:10.0.13-1.0.1.el9_8
  • C
Weak Password Recovery Mechanism for Forgotten Password

<0:10.0.13-1.0.1.el9_8
  • C
Inclusion of Functionality from Untrusted Control Sphere

<0:10.0.13-1.0.1.el9_8
  • C
Authentication Bypass

<0:10.0.13-1.0.1.el9_8
  • C
Deadlock

<0:10.0.13-1.0.1.el9_8
  • C
Link Following

<0:10.0.13-1.0.1.el9_8
  • C
Allocation of Resources Without Limits or Throttling

<0:10.0.13-1.0.1.el9_8
  • C
Race Condition

<0:10.0.13-1.0.1.el9_8
  • C
HTTP Request Smuggling

<0:10.0.13-1.0.1.el9_8
  • C
Cross-site Scripting (XSS)

<0:10.0.13-1.0.1.el9_8
  • C
Algorithmic Complexity

<0:10.0.13-1.0.1.el9_8
  • C
Improper Verification of Cryptographic Signature

<0:10.0.13-1.0.1.el9_8
  • C
Allocation of Resources Without Limits or Throttling

<0:10.0.13-1.0.1.el9_8
  • C
Algorithmic Complexity

<0:10.0.13-1.0.1.el9_8
  • H
Origin Validation Error

<0:10.0.12-1.0.1.el9_8
  • H
Arbitrary Code Injection

<0:10.0.12-1.0.1.el9_8
  • H
Unchecked Input for Loop Condition

<0:10.0.11-1.0.1.el9_8
  • H
Unchecked Return Value

<0:10.0.11-1.0.1.el9_8
  • H
Improper Cross-boundary Removal of Sensitive Data

<0:10.0.11-1.0.1.el9_8
  • H
HTTP Request Smuggling

<0:10.0.11-1.0.1.el9_8
  • H
Link Following

<0:10.0.10-1.0.1.el9_8
  • H
Deserialization of Untrusted Data

<0:10.0.10-1.0.1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:10.0.10-1.0.1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:10.0.10-1.0.1.el9_8
  • H
Access of Resource Using Incompatible Type ('Type Confusion')

<0:10.0.10-1.0.1.el9_8
  • H
Stack-based Buffer Overflow

<0:10.0.10-1.0.1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:10.0.10-1.0.1.el9_8
  • H
Incorrect Implementation of Authentication Algorithm

<0:10.0.10-1.0.1.el9_8
  • H
Insufficient Verification of Data Authenticity

<0:10.0.10-1.0.1.el9_8
  • H
Improper Validation of Specified Type of Input

<0:10.0.10-1.0.1.el9_8
  • H
Improper Encoding or Escaping of Output

<0:10.0.10-1.0.1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:10.0.10-1.0.1.el9_8
  • H
Authentication Bypass

<0:10.0.10-1.0.1.el9_8
  • H
LDAP Injection

<0:10.0.10-1.0.1.el9_8
  • H
Deserialization of Untrusted Data

<0:10.0.10-1.0.1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:10.0.10-1.0.1.el9_8
  • H
Arbitrary Code Injection

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

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

<0:10.0.9-1.0.1.el9_8
  • H
Resource Exhaustion

<0:10.0.9-1.0.1.el9_8
  • H
Improper Input Validation

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

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

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

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

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

<0:10.0.4-1.0.1.el9_7
  • H
Link Following

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

<0:9.0.10-1.0.1.el9_6
  • H
Inadequate Encryption Strength

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

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

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

<0:9.0.3-1.0.1.el9_5
  • H
CVE-2024-43499

<0:9.0.0-1.0.1.el9_5
  • H
CVE-2024-43498

<0:9.0.0-1.0.1.el9_5
  • H
CVE-2024-38229

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

<0:8.0.10-1.0.1.el9_4
  • H
CVE-2024-43483

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

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

<0:8.0.8-1.0.1.el9_4
  • H
CVE-2024-30105

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

<0:8.0.7-1.0.1.el9_4
  • H
CVE-2024-35264

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

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

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

<0:8.0.3-2.0.1.el9_3
  • H
CVE-2024-21404

<0:8.0.2-2.0.1.el9_3
  • H
CVE-2024-21386

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

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

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

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

<0:8.0.0-2.0.1.el9_3
  • M
CVE-2023-36049

<0:8.0.0-2.0.1.el9_3
  • H
CVE-2023-44487

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

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

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

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

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

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

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

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

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

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

<0:7.0.0-0.5.rc2.0.1.el9_1
  • M
CVE-2022-38013

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

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

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

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

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

<0:6.0.5-1.0.1.el9_0