Security readout for executives and security teams
Plain-English summary
This is a Wasmtime/Cranelift bug where some WebAssembly SIMD operations can compute the wrong result on x86_64 hosts. The host running Wasm is described as largely unaffected, but guest programs may behave incorrectly, which can create downstream integrity or availability issues inside the guest workload.
Executive priority
Treat as a targeted medium-priority runtime correctness issue. It is most urgent for services executing third-party or security-sensitive Wasm on x86_64 with SIMD enabled. Routine patching is appropriate unless guest misexecution could affect business-critical decisions.
Technical view
Affected x86_64 SIMD lowerings for `i8x16.swizzle` and `select` with `v128` inputs miscompile WebAssembly semantics. `swizzle` can corrupt a reused mask register; `select` can leave upper 96 bits stale when the condition is zero. aarch64 is not affected; s390x lacked SIMD support in the cited context.
Likely exposure
Exposure is limited to deployments using affected Wasmtime or Cranelift versions on x86_64 with the WebAssembly SIMD proposal enabled, especially where untrusted or complex guest Wasm is executed.
Exploitation context
The bundle states KEV is false and provides no cited evidence of active exploitation. The concern is guest-code misexecution, not a described host escape. Impact depends on whether guest logic can be harmed by incorrect branches or values.
Researcher notes
The advisory frames impact as incorrect WebAssembly semantics in guest execution. Validation should focus on version, architecture, SIMD enablement, and guest dependence on vector operations. Do not assume host compromise from the provided sources.
Mitigation direction
- Upgrade Wasmtime to 0.38.1 or later.
- Upgrade cranelift-codegen and associated Cranelift crates to 0.85.1 or later.
- Disable Wasm SIMD when upgrading is not immediately possible.
- Prioritize x86_64 hosts running guest WebAssembly with SIMD enabled.
- Track the Bytecode Alliance advisory for any revised guidance.
Validation and detection
- Inventory Wasmtime and Cranelift versions in source, lockfiles, and build artifacts.
- Confirm whether affected workloads run on x86_64 hosts.
- Check whether Wasm SIMD is enabled in runtime configuration.
- Identify guest workloads that rely on WebAssembly SIMD or `v128` operations.
- Re-run application regression tests after upgrading or disabling SIMD.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-682: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31104 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L2.22.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-jqwc-c49r-4w2xCVE reference · x_refsource_CONFIRM
- https://github.com/bytecodealliance/wasmtime/pull/4317CVE reference · x_refsource_MISC
- https://github.com/bytecodealliance/wasmtime/pull/4318CVE reference · x_refsource_MISC
- https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_simdCVE reference · x_refsource_MISC
- https://github.com/webassembly/simdCVE reference · x_refsource_MISC
- https://webassembly.github.io/spec/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Calculation
Incorrect Calculation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
