Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

GHSA-65x7-c272-7g7r

HIGHFix: SixLabors/ImageSharp#2688

GHSA-65x7-c272-7g7r is a high-severity (CVSS 7.1) Use After Free vulnerability in SixLabors.ImageSharp. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-65x7-c272-7g7r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Use After Free in SixLabors.ImageSharp

Also known asCVE-2024-27929
Published
Mar 5, 2024
Updated
Mar 6, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Mar 6, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
.NETSixLabors.ImageSharp.NETSixLabors.ImageSharp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A heap-use-after-free flaw was found in ImageSharp's InitializeImage() function of PngDecoderCore.cs file. This vulnerability is triggered when an attacker passes a specially crafted PNG image file to ImageSharp for conversion, potentially leading to information disclosure.

Patches

The problem has been patched. All users are advised to upgrade to v3.1.3 or v2.1.7.

Workarounds

None

References

None

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSixLabors.ImageSharp3.0.0&&< 3.1.33.1.3
.NETNuGetSixLabors.ImageSharpall versions2.1.7
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for SixLabors.ImageSharp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update SixLabors.ImageSharp to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65x7-c272-7g7r is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-65x7-c272-7g7r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-65x7-c272-7g7r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A heap-use-after-free flaw was found in ImageSharp's InitializeImage() function of PngDecoderCore.cs file. This vulnerability is triggered when an attacker passes a specially crafted PNG image file to ImageSharp for conversion, potentially leading to information disclosure. ### Patches The problem has been patched. All users are advised to upgrade to v3.1.3 or v2.1.7. ### Workarounds None ### References None
O3 Security · Impact-Aware SCA

Is GHSA-65x7-c272-7g7r in your dependencies?

O3 detects GHSA-65x7-c272-7g7r across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-65x7-c272-7g7r: Use After Free in… | O3 Security