# CVE-2019-1301: High severity vulnerability that affects System.Management.Automation > Attackers can cause a denial of service in .NET Core applications by sending improperly handled web requests. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Sep 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-62gw-3rmj-wmp2, RHSA-2019:2731, RHSA-2019:2732 ## What is CVE-2019-1301? CVE-2019-1301 is a high-severity denial of service vulnerability in Microsoft .NET Core, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A denial of service vulnerability exists when .NET Core improperly handles web requests, aka '.NET Core Denial of Service Vulnerability'. ## Which versions are affected by CVE-2019-1301? 4 open source packages ship an affected version, including System.Management.Automation. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `System.Management.Automation` | NuGet | From 6.0.0 | 6.1.6 | | `System.Management.Automation` | NuGet | From 6.0.0 | 6.1.6 | | `System.Management.Automation` | NuGet | From 6.2.0 | 6.2.3 | | `System.Management.Automation` | NuGet | From 6.2.0 | 6.2.3 | | `dotnet` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.509-1.el8_0 | | `dotnet-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.509-1.el8_0 | | `dotnet-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.509-1.el8_0 | | `dotnet-host` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.13-1.el8_0 | | `dotnet-host-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.13-1.el8_0 | | `dotnet-host-fxr-2.1` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.13-1.el8_0 | | `dotnet-host-fxr-2.1-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.13-1.el8_0 | | `dotnet-runtime-2.1` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.13-1.el8_0 | | `dotnet-runtime-2.1-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.13-1.el8_0 | | `dotnet-sdk-2.1` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.509-1.el8_0 | | `dotnet-sdk-2.1.5xx` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.509-1.el8_0 | | `dotnet-sdk-2.1.5xx-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.509-1.el8_0 | | `rh-dotnet21` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1-12.el7 | | `rh-dotnet21-dotnet` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.509-1.el7 | | `rh-dotnet21-dotnet-debuginfo` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.509-1.el7 | | `rh-dotnet21-dotnet-host` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.13-1.el7 | | `rh-dotnet21-dotnet-runtime-2.1` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.13-1.el7 | | `rh-dotnet21-dotnet-sdk-2.1` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.509-1.el7 | | `rh-dotnet21-dotnet-sdk-2.1.5xx` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.509-1.el7 | | `rh-dotnet21-runtime` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1-12.el7 | | `rh-dotnet22` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2-9.el7 | | `rh-dotnet22-dotnet` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.109-1.el7 | | `rh-dotnet22-dotnet-debuginfo` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.109-1.el7 | | `rh-dotnet22-dotnet-host` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.7-1.el7 | | `rh-dotnet22-dotnet-host-fxr-2.2` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.7-1.el7 | | `rh-dotnet22-dotnet-runtime-2.2` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.7-1.el7 | | `rh-dotnet22-dotnet-sdk-2.2` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.109-1.el7 | | `rh-dotnet22-dotnet-sdk-2.2.1xx` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.109-1.el7 | | `rh-dotnet22-runtime` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2-9.el7 | Products: Microsoft .Net Core, Microsoft Powershell Core. ## How do I fix CVE-2019-1301? Upgrade System.Management.Automation to a fixed version for your release line: 6.1.6 or 6.2.3. ## Is CVE-2019-1301 being exploited? There is no known exploitation of CVE-2019-1301 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft .NET Core - [CVE-2020-1147](https://insights.sbomify.com/CVE-2020-1147/): Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution (high 7.8, exploited in the wild) - [CVE-2020-0605](https://insights.sbomify.com/CVE-2020-0605/): Code injection in .NET Core (high 8.8) - [CVE-2020-0606](https://insights.sbomify.com/CVE-2020-0606/): Remote code execution in Microsoft.WindowsDesktop.App.Ref (high 8.8) - [CVE-2019-0820](https://insights.sbomify.com/CVE-2019-0820/): Regular Expression Denial of Service in System.Text.RegularExpressions (high 7.5) - [CVE-2019-0980](https://insights.sbomify.com/CVE-2019-0980/): Denial of service in ASP.NET Core (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1301 and fix it if it is affected. What it is: CVE-2019-1301 is a high-severity denial of service vulnerability in Microsoft .NET Core, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-1301 in the wild and no public exploit code. Affected packages and fixed versions: - System.Management.Automation (NuGet): affected from 6.0.0; fixed in 6.1.6 - System.Management.Automation (NuGet): affected from 6.0.0; fixed in 6.1.6 - System.Management.Automation (NuGet): affected from 6.2.0; fixed in 6.2.3 - System.Management.Automation (NuGet): affected from 6.2.0; fixed in 6.2.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-1301/ (Markdown: https://insights.sbomify.com/CVE-2019-1301/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1301 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1301 - OSV: https://osv.dev/vulnerability/CVE-2019-1301 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1301/ Summaries are generated and may contain mistakes; the official description above is the record.