LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48105: An heap overflow vulnerability was discovered in Bytecode alliance wasm-micro-runtime v.1.2.3 allows a remo...

An heap overflow vulnerability was discovered in Bytecode alliance wasm-micro-runtime v.1.2.3 allows a remote attacker to cause a denial of service via the wasm_loader_prepare_bytecode function in core/iwasm/interpreter/wasm_loader.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-48105 reports a heap overflow in Bytecode Alliance wasm-micro-runtime v1.2.3. A remote attacker may be able to cause denial of service when the runtime prepares WebAssembly bytecode. Business impact is most relevant where untrusted or externally supplied Wasm modules are loaded.

Executive priority

Treat this as a targeted availability risk, not a confirmed widespread emergency. Prioritize environments that run customer-supplied or internet-sourced WebAssembly, and ask engineering to confirm exposure and upstream patch status.

Technical view

The reported flaw is a heap overflow in wasm_loader_prepare_bytecode within core/iwasm/interpreter/wasm_loader.c. The CVE description names denial of service as the impact. The source bundle provides no CVSS score, CWE, complete affected-product metadata, or confirmed fixed release.

Likely exposure

Exposure is likely limited to systems that embed wasm-micro-runtime v1.2.3 or process WebAssembly using that runtime, especially from remote or untrusted sources. The provided affected-product metadata is incomplete.

Exploitation context

The CVE is not listed as KEV in the bundle, and no cited source confirms active exploitation. The public description indicates remote denial of service, but does not provide safe operational detail on exploitability conditions.

Researcher notes

Evidence is sparse: the CVE description identifies function, file, version, and denial-of-service impact, but omits CVSS, CWE, and full affected-product records. Avoid expanding scope beyond wasm-micro-runtime v1.2.3 without additional vendor evidence.

Mitigation direction

  • Inventory products and services embedding wasm-micro-runtime, especially version 1.2.3.
  • Avoid accepting untrusted WebAssembly modules where this runtime is in use.
  • Review Bytecode Alliance issue 2726 and the referenced upstream commit.
  • Apply vendor or upstream guidance when a confirmed fixed build is identified.
  • Isolate Wasm-loading services to reduce impact from crashes or restarts.

Validation and detection

  • Confirm whether wasm-micro-runtime is present directly or through dependencies.
  • Check embedded runtime versions against the reported v1.2.3 exposure.
  • Review code paths that call or wrap WebAssembly loading from external inputs.
  • Verify whether deployed builds include the referenced upstream change.
  • Confirm monitoring detects crashes in services that load WebAssembly modules.
Prepared
Confidence
medium
Sources
4

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.

cve · low confidence lookup

CVE-2023-48105 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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