CVE-2022-39394: Wasmtime Wasmtime_trap_code C API Function Has Vulnerability

LOW
Advisory Identifier: GHSA-h84q-m8rr-3v9q
Share
CVSS 3.8
CWE-787
Published
Advisory Summary

CVE-2022-39394 is a LOW (CVSS 3.8) wasmtime_trap_code c api function has vulnerability (CWE-787: Out-of-bounds Write) affecting Wasmtime libraries in the crates.io ecosystem. The issue involves wasmtime_trap_code c api function has out of bounds write vulnerability. Remediation is available by upgrading affected packages to version 2.0.2, 1.0.2.

CVE-2022-39394 at a Glance

CVE Identifier CVE-2022-39394
GHSA Identifier GHSA-h84q-m8rr-3v9q
Severity LOW
CVSS v3.1 Base Score 3.8
CWE Classification CWE-787: Out-of-bounds Write
Affected Product Wasmtime
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 3.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2022-39394

To remediate this vulnerability, upgrade all affected Wasmtime dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wasmtime fixed: 2.0.2 
Upgrade wasmtime to 2.0.2
wasmtime fixed: 1.0.2 
Upgrade wasmtime to 1.0.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for wasmtime

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-39394, inspect your project dependencies for Wasmtime:

inspect dependencies for wasmtime

Analyze the terminal output to locate any version of Wasmtime in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-787: Out-of-bounds Write, where the product writes data past the end, or before the beginning, of the intended buffer. In Wasmtime, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 * [Definition of `wasmtime_trap_code`](https://docs.wasmtime.dev/c-api/trap_8h.html#a6580f4f209d3eaebb6e8b9a901a30b7a) * [Mailing list announcement](https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA) * [Patch to fix for `main` branch](https://github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493) ### For more information If you have any questions or comments about this advisory: * Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime) * Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/)

CVE-2022-39394 Affected Wasmtime Versions

2 component(s)
Fixed Versions:
2.0.21.0.2
Product / Package Ecosystem Affected Versions Fixed Version
wasmtime
 crates.io
≥ 2.0.0
< 2.0.2
2.0.2
wasmtime
 crates.io
< 1.0.2
1.0.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h84q-m8rr-3v9q
NVD — CVE-2022-39394 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-39394
Security Fix Commit FIX COMMIT
https://github.com/bytecodealliance/wasmtime/commit/087d9d7becf7422b3f872a3bcd5d97bb7ce7ff36
Security Fix Commit FIX COMMIT
https://github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493
Wasmtime Source Repository REPOSITORY
https://github.com/bytecodealliance/wasmtime
groups.google.com/a/bytecodealliance.... WEB
https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2022-0097.html

Frequently Asked Questions

What is CVE-2022-39394?
CVE-2022-39394 is a security vulnerability in Wasmtime involving wasmtime_trap_code C API function has out of bounds write vulnerability under CWE-787: Out-of-bounds Write.
Which Wasmtime versions are affected?
Affected versions include releases prior to 2.0.2, 1.0.2 across affected packages: wasmtime.
What version fixes CVE-2022-39394?
Upgrading to 2.0.2, 1.0.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is wasmtime affected?
Yes, wasmtime is affected in releases prior to 2.0.2, 1.0.2. Upgrade your dependency to 2.0.2, 1.0.2 or later.
What is the CVSS score of CVE-2022-39394?
CVE-2022-39394 has a CVSS v3.1 base score of 3.8 (LOW) with vector string CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L.
What CWE is associated with CVE-2022-39394?
CVE-2022-39394 is classified under CWE-787: Out-of-bounds Write (The product writes data past the end, or before the beginning, of the intended buffer.).
How can I check crates.io dependencies for CVE-2022-39394?
Run the dependency tree command: 'inspect dependencies for wasmtime'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h84q-m8rr-3v9q",
  "modified" : "2025-05-02T12:51:45Z",
  "published" : "2024-02-01T00:15:47Z",
  "aliases" : [ "CVE-2022-39394" ],
  "summary" : "wasmtime_trap_code C API function has out of bounds write vulnerability",
  "details" : "### Impact\n\nThere 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.\n\n### Patches\n\nThis bug has been patched and users should upgrade to Wasmtime 2.0.2.\n\n### Workarounds\n\nThis 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.\n\n### References\n\n* [Definition of `wasmtime_trap_code`](https://docs.wasmtime.dev/c-api/trap_8h.html#a6580f4f209d3eaebb6e8b9a901a30b7a)\n* [Mailing list announcement](https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA)\n* [Patch to fix for `main` branch](https://github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)\n* Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "wasmtime"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.0.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "wasmtime"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h84q-m8rr-3v9q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-39394"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/wasmtime/commit/087d9d7becf7422b3f872a3bcd5d97bb7ce7ff36"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/wasmtime/commit/5b6d5e78de106503b3b9add218bb3d2b1d63c493"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bytecodealliance/wasmtime"
  }, {
    "type" : "WEB",
    "url" : "https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/c1HBDDJwNPA"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2022-0097.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-787" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-02-01T00:15:47Z",
    "nvd_published_at" : "2022-11-10T20:15:00Z"
  }
}