Security readout for executives and security teams
Plain-English summary
This CVE describes a denial-of-service risk in Go-Ethereum 1.10.12 and earlier. A malicious peer can force a victim node to drop pending transactions from memory, disrupting transaction handling. The source bundle does not provide a CVSS score, vendor fix, or evidence of active exploitation.
Executive priority
Treat as a targeted availability risk for Ethereum infrastructure, not a general enterprise compromise issue. Prioritize if your business depends on Go-Ethereum nodes for transaction submission, monitoring, custody workflows, or blockchain service availability.
Technical view
The reported design flaw allows an attacker node to send 5,120 high-gas-price future transactions in one message. That can purge pending transactions from the victim Go-Ethereum node mempool, causing DoS against transaction availability or propagation. Public details are limited to the CVE description and cited research references.
Likely exposure
Exposure is most relevant to organizations operating Go-Ethereum/geth nodes at version 1.10.12 or older, especially nodes accepting peer traffic from untrusted networks.
Exploitation context
The bundle says exploitation requires an attacker-controlled node sending crafted future transactions. CISA KEV status is false, and no cited source in the bundle states active exploitation in the wild.
Researcher notes
The record lacks CVSS, CWE, precise affected CPEs, and a named fixed release. The technical mechanism is specific enough to guide exposure review, but remediation should be anchored to current Go-Ethereum advisories or release notes.
Mitigation direction
- Identify Go-Ethereum/geth nodes running 1.10.12 or older.
- Check Go-Ethereum vendor guidance for fixed versions or official workarounds.
- Prioritize remediation for public or business-critical Ethereum nodes.
- Monitor affected nodes for abnormal mempool eviction or transaction propagation failures.
Validation and detection
- Inventory node software names and versions across production and staging.
- Confirm whether any deployed Go-Ethereum version is 1.10.12 or older.
- Review node logs and metrics for unexplained mempool churn or transaction drops.
- Document whether vendor guidance names a patch or mitigation before changing controls.
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.
CVE-2022-23327 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://tristartom.github.io/docs/ccs21.pdfCVE reference, mitre
- https://dl.acm.org/doi/pdf/10.1145/3460120.3485369CVE reference, mitre
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.