Homepage

dotnet-sdk-8.0-source-built-artifacts

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the dotnet-sdk-8.0-source-built-artifacts 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
Access of Resource Using Incompatible Type ('Type Confusion')

<0:8.0.129-1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:8.0.129-1.el9_8
  • H
Improper Encoding or Escaping of Output

<0:8.0.129-1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:8.0.129-1.el9_8
  • H
Arbitrary Code Injection

<0:8.0.129-1.el9_8
  • H
Deserialization of Untrusted Data

<0:8.0.129-1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:8.0.129-1.el9_8
  • H
Deserialization of Untrusted Data

<0:8.0.129-1.el9_8
  • H
Authentication Bypass

<0:8.0.129-1.el9_8
  • H
Stack-based Buffer Overflow

<0:8.0.129-1.el9_8
  • H
Link Following

<0:8.0.129-1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:8.0.129-1.el9_8
  • H
Improper Validation of Specified Type of Input

<0:8.0.129-1.el9_8
  • H
Insufficient Verification of Data Authenticity

<0:8.0.129-1.el9_8
  • H
LDAP Injection

<0:8.0.129-1.el9_8
  • H
Allocation of Resources Without Limits or Throttling

<0:8.0.129-1.el9_8
  • H
Incorrect Implementation of Authentication Algorithm

<0:8.0.129-1.el9_8
  • H
Resource Exhaustion

<0:8.0.128-1.el9_8
  • H
Link Following

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

<0:8.0.127-1.el9_8
  • H
Resource Exhaustion

<0:8.0.127-1.el9_8
  • H
Improper Input Validation

<0:8.0.126-1.el9_7
  • H
Improper Input Validation

<0:8.0.126-1.el9_7
  • H
Improper Neutralization of Special Elements

<0:8.0.126-1.el9_7
  • H
Resource Exhaustion

<0:8.0.126-1.el9_7
  • H
Allocation of Resources Without Limits or Throttling

<0:8.0.125-1.el9_7
  • H
HTTP Request Smuggling

<0:8.0.121-1.el9_6
  • H
Inadequate Encryption Strength

<0:8.0.121-1.el9_6
  • H
Link Following

<0:8.0.121-1.el9_6
  • H
Untrusted Search Path

<0:8.0.117-1.el9_6
  • H
External Control of File Name or Path

<0:8.0.116-1.el9_6
  • H
CVE-2025-24070

<0:8.0.114-1.el9_5
  • H
CVE-2024-43485

<0:8.0.110-1.el9_4
  • H
CVE-2024-43484

<0:8.0.110-1.el9_4
  • H
CVE-2024-43483

<0:8.0.110-1.el9_4
  • H
CVE-2024-38229

<0:8.0.110-1.el9_4
  • M
CVE-2024-38167

<0:8.0.108-1.el9_4
  • H
CVE-2024-38095

<0:8.0.107-1.el9_4
  • H
CVE-2024-35264

<0:8.0.107-1.el9_4
  • H
CVE-2024-30105

<0:8.0.107-1.el9_4
  • H
Race Condition

<0:8.0.105-1.el9_4
  • H
CVE-2024-30045

<0:8.0.105-1.el9_4
  • M
CVE-2024-21392

<0:8.0.103-2.el9_3
  • H
CVE-2024-21404

<0:8.0.102-2.el9_3
  • H
CVE-2024-21386

<0:8.0.102-2.el9_3
  • H
CVE-2024-21319

<0:8.0.101-1.el9_3
  • H
CVE-2024-0057

<0:8.0.101-1.el9_3
  • H
CVE-2024-0056

<0:8.0.101-1.el9_3
  • M
CVE-2023-36558

<0:8.0.100-2.el9_3
  • M
CVE-2023-36049

<0:8.0.100-2.el9_3