Advisory

GHSA-h84q-m8rr-3v9q

Also known as: CVE-2022-39394, RUSTSEC-2022-0097

Summary

wasmtime_trap_code C API function has out of bounds write vulnerability

Details

Impact

There is a bug in Wasmtime's C API implementation where the definition of the wasmtime_trap_code does not match its declared signature in the wasmtime/trap.h header file. This discrepancy causes the function implementation to perform a 4-byte write into a 1-byte buffer provided by the caller. This can lead to three zero bytes being written beyond the 1-byte location provided by the caller.

Patches

This bug has been patched and users should upgrade to Wasmtime 2.0.2.

Workarounds

This can be worked around by providing a 4-byte buffer casted to a 1-byte buffer when calling wasmtime_trap_code. Users of the wasmtime crate are not affected by this issue, only users of the C API function wasmtime_trap_code are affected.

References

For more information

If you have any questions or comments about this advisory:

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-02-01 00:15 UTC
Modified
2025-05-02 12:51 UTC

Affected packages and fixes

wasmtime

crates.io · All systems

Affected

  • introduced 2.0.0, fixed 2.0.2 (semver)

Fixed versions

2.0.2

Fix

  • Fixed version 2.0.2
    cargo update -p wasmtime --precise 2.0.2

wasmtime

crates.io · All systems

Affected

  • introduced 0, fixed 1.0.2 (semver)

Fixed versions

1.0.2

Fix

  • Fixed version 1.0.2
    cargo update -p wasmtime --precise 1.0.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences