LiveActive security incident?Get immediate response
CVE Record

CVE-2022-39974: WASM3 v0.5.0 was discovered to contain a segmentation fault via the component op_Select_i32_srs in wasm3/so...

WASM3 v0.5.0 was discovered to contain a segmentation fault via the component op_Select_i32_srs in wasm3/source/m3_exec.h.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a crash bug in WASM3 v0.5.0. If an exposed service uses this interpreter on untrusted WebAssembly input, an attacker could potentially cause service disruption. The documented impact is availability, not data theft or code execution.

Executive priority

Prioritize remediation if WASM3 v0.5.0 runs in customer-facing or multi-tenant workflows. If usage is internal and trusted-only, handle as a dependency risk but still track vendor guidance.

Technical view

WASM3 v0.5.0 reportedly contains a segmentation fault in op_Select_i32_srs within wasm3/source/m3_exec.h. The CVSS 3.1 score is 7.5, driven by remote, unauthenticated, low-complexity availability impact. The source maps it to CWE-119.

Likely exposure

Exposure is most likely where WASM3 v0.5.0 is embedded in applications or services that process untrusted WebAssembly modules. The CVE data lacks CPEs and normalized affected product metadata.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat exploitation status as unconfirmed; the available evidence supports a denial-of-service risk through a crash condition.

Researcher notes

Evidence is sparse. The CVE names WASM3 v0.5.0 and a specific interpreter component, but the affected vendor/product fields are n/a and no patch details are included in the bundle.

Mitigation direction

  • Inventory applications embedding WASM3 and identify any v0.5.0 usage.
  • Check the WASM3 project issue and vendor guidance for fixed versions or recommended changes.
  • Avoid processing untrusted WebAssembly with affected deployments until guidance is applied.
  • Isolate affected interpreter workloads from critical service paths where feasible.
  • Add monitoring for crashes in services that run WASM3.

Validation and detection

  • Review SBOMs, lockfiles, vendored code, and build manifests for WASM3 v0.5.0.
  • Confirm whether externally supplied WebAssembly can reach the WASM3 interpreter.
  • Review crash telemetry for segmentation faults involving wasm3/source/m3_exec.h.
  • Verify compensating controls around WebAssembly upload, validation, and execution boundaries.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-119: 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 lookup
cve · low confidence lookup

CVE-2022-39974 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-39974Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-119

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs