# ALEA-2022:0322: .NET Core 3.1 bugfix and enhancement update


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 31 Jan 2022

## What is ALEA-2022:0322?

ALEA-2022:0322 is a vulnerability in aspnetcore-runtime-3.1, published on 31 Jan 2022. 

### 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.416 and Runtime 3.1.22 [almalinux-8.5.0.z] (BZ#2031429)

## Which versions are affected by ALEA-2022:0322?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aspnetcore-runtime-3.1` | AlmaLinux:8 | All versions | 3.1.22-3.el8_5 |
| `aspnetcore-targeting-pack-3.1` | AlmaLinux:8 | All versions | 3.1.22-3.el8_5 |
| `dotnet-apphost-pack-3.1` | AlmaLinux:8 | All versions | 3.1.22-3.el8_5 |
| `dotnet-build-reference-packages` | AlmaLinux:8 | All versions | 0-11.20211215git045b288.el8_5 |
| `dotnet-hostfxr-3.1` | AlmaLinux:8 | All versions | 3.1.22-3.el8_5 |
| `dotnet-runtime-3.1` | AlmaLinux:8 | All versions | 3.1.22-3.el8_5 |
| `dotnet-sdk-3.1` | AlmaLinux:8 | All versions | 3.1.416-3.el8_5 |
| `dotnet-sdk-3.1-source-built-artifacts` | AlmaLinux:8 | All versions | 3.1.416-3.el8_5 |
| `dotnet-targeting-pack-3.1` | AlmaLinux:8 | All versions | 3.1.22-3.el8_5 |
| `dotnet-templates-3.1` | AlmaLinux:8 | All versions | 3.1.416-3.el8_5 |

## How do I fix ALEA-2022:0322?

Upgrade to a fixed version.

## Is ALEA-2022:0322 being exploited?

There is no known exploitation of ALEA-2022:0322 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALEA-2022:0322 and fix it if it is affected.

What it is: ALEA-2022:0322 is a vulnerability in aspnetcore-runtime-3.1, published on 31 Jan 2022. 
Exploitation: There is no known exploitation of ALEA-2022:0322 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/ALEA-2022-0322/ (Markdown: https://insights.sbomify.com/ALEA-2022-0322/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2022:0322

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