# ALBA-2021:3817: .NET Core 3.1 bugfix update


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 12 Oct 2021

## What is ALBA-2021:3817?

ALBA-2021:3817 is a vulnerability in aspnetcore-runtime-3.1, published on 12 Oct 2021. 

### Official description

.NET Core is a managed-software framework. It implements a subset of the .NET framework APIs and several new APIs, and it includes a CLR implementation.

Bug Fix(es) and Enhancement(s):

* Update .NET Core 3.1 to SDK 3.1.120 and Runtime 3.1.20 [almalinux-8.4.0.z] (BZ#2011821)

## Which versions are affected by ALBA-2021:3817?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aspnetcore-runtime-3.1` | AlmaLinux:8 | All versions | 3.1.20-1.el8_4 |
| `aspnetcore-targeting-pack-3.1` | AlmaLinux:8 | All versions | 3.1.20-1.el8_4 |
| `dotnet-apphost-pack-3.1` | AlmaLinux:8 | All versions | 3.1.20-1.el8_4 |
| `dotnet-hostfxr-3.1` | AlmaLinux:8 | All versions | 3.1.20-1.el8_4 |
| `dotnet-runtime-3.1` | AlmaLinux:8 | All versions | 3.1.20-1.el8_4 |
| `dotnet-sdk-3.1` | AlmaLinux:8 | All versions | 3.1.120-1.el8_4 |
| `dotnet-targeting-pack-3.1` | AlmaLinux:8 | All versions | 3.1.20-1.el8_4 |
| `dotnet-templates-3.1` | AlmaLinux:8 | All versions | 3.1.120-1.el8_4 |

## How do I fix ALBA-2021:3817?

Upgrade to a fixed version.

## Is ALBA-2021:3817 being exploited?

There is no known exploitation of ALBA-2021:3817 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2021:3817 and fix it if it is affected.

What it is: ALBA-2021:3817 is a vulnerability in aspnetcore-runtime-3.1, published on 12 Oct 2021. 
Exploitation: There is no known exploitation of ALBA-2021:3817 in the wild and no public exploit code.

Affected product: aspnetcore-runtime-3.1. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/ALBA-2021-3817/ (Markdown: https://insights.sbomify.com/ALBA-2021-3817/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:3817

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2021-3817/
Summaries are generated and may contain mistakes; the official description above is the record.