CVE-2022-29918

What it actually does

Memory safety bugs in the affected software versions cause memory corruption that can be leveraged to execute arbitrary code.

Why it matters to the business

Attackers could gain full control of affected systems, resulting in data theft, ransomware deployment, or unauthorized access to internal resources; the long window since disclosure increases exposure for unpatched environments with high downstream usage.

How an attack unfolds

An attacker crafts specially formed input that triggers one of the memory corruption conditions when processed by the vulnerable runtime or browser; with sufficient effort this leads to arbitrary code execution. No named threat actors or ransomware campaigns are associated with this issue.

How to fix it

Upgrade all listed packages to the stated fixed versions: dotnet6 on Ubuntu 22.04 to 6.0.109-0ubuntu1~22.04.1; Microsoft.AspNetCore.App.Runtime packages to 3.1.29 or 6.0.9 as applicable for each architecture and OS flavor. Remove or isolate any remaining older installations.

How to confirm the fix worked

Verify installed package versions match or exceed the listed fixed releases using package managers or runtime version queries; re-run any available memory-safety test suites or fuzzers against the updated binaries.

Typical attack path

1. Identify a target running an unpatched version of the affected product
2. Deliver malicious content via network request, file, or web page
3. Trigger the memory safety flaw to corrupt process memory
4. Achieve arbitrary code execution within the process context

How to detect it

Review application and system logs for unexpected process crashes or memory-related errors around the time of suspected activity; correlate with network or file access from untrusted sources.

What your security team should do

• Prioritize patching all internet-facing or high-value systems within the next 30 days given the public disclosure timeline
• Add the fixed package versions to approved software lists and block older builds via policy
• Scan internal repositories and build pipelines for any pinned vulnerable versions