An issue was discovered in the arrayfire crate before 3.6.0 for Rust. Addition of the repr() attribute to an enum is mishandled, leading to memory corruption.

These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.

CVE-2018-20998 · Microsoft / collected KEV context

EUVD-2019-0020

GHSA-69fv-gw6g-8ccg

PYSEC-2019-144

RUSTSEC-2018-0011

cve-program · CVE-2018-20998

• https://rustsec.org/advisories/RUSTSEC-2018-0011.html

euvd · EUVD-2019-0020

• https://rustsec.org/advisories/RUSTSEC-2018-0011.html

nvd · CVE-2018-20998

• https://rustsec.org/advisories/RUSTSEC-2018-0011.html

osv · GHSA-69fv-gw6g-8ccg

• https://nvd.nist.gov/vuln/detail/CVE-2018-20998
• https://github.com/arrayfire/arrayfire-rust/pull/177
• https://github.com/arrayfire/arrayfire-rust/commit/a5256f3e5e23b83eaad69699e0b04653aba04fb8
• https://github.com/arrayfire/arrayfire-rust
• https://github.com/pypa/advisory-database/tree/main/vulns/arrayfire/PYSEC-2019-144.yaml
• https://rustsec.org/advisories/RUSTSEC-2018-0011.html

osv · RUSTSEC-2018-0011

• https://crates.io/crates/arrayfire
• https://rustsec.org/advisories/RUSTSEC-2018-0011.html
• https://github.com/arrayfire/arrayfire-rust/pull/177

No related operational record is retained in the current change model.