GHSA-h84q-m8rr-3v9q

Suggest an improvement
Source
https://github.com/advisories/GHSA-h84q-m8rr-3v9q
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/02/GHSA-h84q-m8rr-3v9q/GHSA-h84q-m8rr-3v9q.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-h84q-m8rr-3v9q
Aliases
Published
2024-02-01T00:15:47Z
Modified
2024-02-01T00:15:47Z
Severity
  • 3.8 (Low) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L CVSS Calculator
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:

Database specific
{
    "nvd_published_at": "2022-11-10T20:15:00Z",
    "cwe_ids": [
        "CWE-787"
    ],
    "severity": "LOW",
    "github_reviewed": true,
    "github_reviewed_at": "2024-02-01T00:15:47Z"
}
References

Affected packages

crates.io / wasmtime

Package

Affected ranges

Type
SEMVER
Events
Introduced
2.0.0
Fixed
2.0.2

crates.io / wasmtime

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.0.2