CVE-2022-39394
3.8 · LOWOverview
CVE-2022-39394 is a low-severity vulnerability affecting bytecodealliance wasmtime. It was published on November 10, 2022 and has a CVSS 3.1 base score of 3.8 (LOW).
This vulnerability has a CVSS 3.1 base score of 3.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
Technical Description
Wasmtime is a standalone runtime for WebAssembly. Prior to version 2.0.2, 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. This bug has been patched and users should upgrade to Wasmtime 2.0.2. This bug 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.
Remediation
Check the references section for vendor advisories and patches from bytecodealliance. Update wasmtime to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| bytecodealliance | wasmtime | >= 0, < 1.0.2 | Affected |
References
Frequently Asked Questions
What is CVE-2022-39394?
CVE-2022-39394 is a low-severity vulnerability affecting bytecodealliance wasmtime. It was published on November 10, 2022 and has a CVSS 3.1 base score of 3.8 (LOW).
How severe is CVE-2022-39394?
This vulnerability has a CVSS 3.1 base score of 3.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2022-39394?
Check the references section for vendor advisories and patches from bytecodealliance. Update wasmtime to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2022-39394?
CyberStrike's AI-powered security agents can automatically detect CVE-2022-39394 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2022
View all →Abitrary file access vulnerability in Samsung Email prior to 6.1.60.16 allows attacker to read isola
Vulnerability in the Oracle Solaris product of Oracle Systems (component: Install). The supported ve
PendingIntent hijacking vulnerability in KnoxPrivacyNoticeReceiver prior to SMR Feb-2022 Release 1 a
PendingIntent hijacking vulnerability in CpaReceiver prior to SMR Feb-2022 Release 1 allows local at
PendingIntent hijacking vulnerability in DataUsageReminderReceiver prior to SMR Feb-2022 Release 1 a
An insecure data storage vulnerability allows a physical attacker with root privileges to retrieve T
Redis is an in-memory database that persists on disk. By exploiting weaknesses in the Lua script exe
In JetBrains IntelliJ IDEA before 2022.1 reflected XSS via error messages in internal web server was
In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed
Improper file permissions in the CommandPost, Collector, and Sensor components of Fidelis Network an
In finishDrawingWindow of WindowManagerService.java, there is a possible tapjacking due to improper
In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible