Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀
🦀 crates.io🐍 PyPI
Not in CISA KEV
CRITICAL severity

GHSA-69fv-gw6g-8ccg

CRITICALFix: arrayfire/arrayfire-rust#177

GHSA-69fv-gw6g-8ccg is a critical-severity (CVSS 9.8) Buffer Overflow vulnerability in arrayfire. O3 Security confirms whether GHSA-69fv-gw6g-8ccg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Potential memory corruption in arrayfire

Also known asCVE-2018-20998RUSTSEC-2018-0011
Published
Aug 25, 2021
Updated
Sep 12, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 12, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🦀arrayfire🐍arrayfire

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

Description

The attribute repr() added to enums to be compatible with C-FFI caused memory corruption on MSVC toolchain.

arrayfire crates <= version 3.5.0 do not have this issue when used with Rust versions 1.27 or earlier. The issue only started to appear since Rust version 1.28.

The issue seems to be interlinked with which version of Rust is being used.

The issue was fixed in crate 3.6.0.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioarrayfireall versions3.6.0
🐍PyPIarrayfireall versions3.6.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for arrayfire. 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 arrayfire to 3.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-69fv-gw6g-8ccg 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-69fv-gw6g-8ccg 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-69fv-gw6g-8ccg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The attribute repr() added to enums to be compatible with C-FFI caused memory corruption on MSVC toolchain. arrayfire crates <= version 3.5.0 do not have this issue when used with Rust versions 1.27 or earlier. The issue only started to appear since Rust version 1.28. The issue seems to be interlinked with which version of Rust is being used. The issue was fixed in crate 3.6.0.
O3 Security · Impact-Aware SCA

Is GHSA-69fv-gw6g-8ccg in your dependencies?

O3 detects GHSA-69fv-gw6g-8ccg across crates.io, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-69fv-gw6g-8ccg: Potential memory… | O3 Security