LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23328: A design flaw in all versions of Go-Ethereum allows an attacker node to send 5120 pending transactions of a...

A design flaw in all versions of Go-Ethereum allows an attacker node to send 5120 pending transactions of a high gas price from one account that all fully spend the full balance of the account to a victim Geth node, which can purge all of pending transactions in a victim node's memory pool and then occupy the memory pool to prevent new transactions from entering the pool, resulting in a denial of service (DoS).

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-23328 is a denial-of-service issue in Go-Ethereum/Geth node transaction handling. A hostile peer can disrupt a victim node’s pending-transaction pool and prevent new transactions from entering it. The business impact is degraded availability for services that depend on Geth node transaction processing.

Executive priority

Address as an availability risk for Ethereum infrastructure, not as a confirmed data compromise. Prioritize environments where Geth downtime or transaction admission failure would affect customers, trading, monitoring, or operational continuity.

Technical view

The CVE describes a design flaw where an attacker-controlled node can send many high-gas pending transactions from one account that spend the account balance. This can purge pending transactions from a victim Geth node’s mempool and then occupy that pool, causing denial of service. Source data does not provide CVSS, patched versions, or CWE mapping.

Likely exposure

Exposure is most relevant to organizations operating Go-Ethereum/Geth nodes that accept peer traffic and rely on mempool availability. The source bundle says all versions of Go-Ethereum, but does not provide precise affected version ranges or fixed releases.

Exploitation context

The CVE source describes a feasible attacker-node scenario, but the bundle marks KEV as false and provides no cited evidence of active exploitation. Treat exploitation status as unconfirmed from the provided sources.

Researcher notes

Evidence is limited to the CVE description and linked research references. The record identifies a mempool DoS design flaw but lacks CVSS, CWE, patch details, and precise versions. Do not infer active exploitation or remediation beyond checking Go-Ethereum guidance.

Mitigation direction

  • Check current Go-Ethereum/Geth vendor guidance for fixed versions or operational mitigations.
  • Inventory Geth nodes that support production transaction submission or monitoring workflows.
  • Prioritize updates where Geth nodes are externally peered or availability-critical.
  • Monitor mempool saturation, transaction admission failures, and node availability anomalies.
  • Review peer exposure and node isolation using existing Ethereum node hardening practices.

Validation and detection

  • Confirm whether any production systems run Go-Ethereum/Geth nodes.
  • Record exact Geth versions and compare them with vendor guidance.
  • Review logs and metrics for abnormal pending-transaction pool churn.
  • Validate alerting for mempool exhaustion and transaction processing disruption.
  • Document any compensating controls around peer access and node redundancy.
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-2022-23328 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
1ADP providers
3Source links

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

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.