LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22570: Memcached 1.6.0 before 1.6.3 allows remote attackers to cause a denial of service (daemon crash) via a craf...

Memcached 1.6.0 before 1.6.3 allows remote attackers to cause a denial of service (daemon crash) via a crafted meta command.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects Memcached 1.6.0 before 1.6.3 and can let a remote attacker crash the daemon. The main business impact is service disruption for applications relying on Memcached for caching or session-like performance support.

Executive priority

Treat this as a targeted availability risk. It is most urgent where Memcached supports customer-facing services or is reachable outside tightly controlled internal networks.

Technical view

The source describes a denial-of-service issue in Memcached meta command handling. A crafted meta command can remotely trigger a daemon crash. The bundle does not provide CVSS, CWE, root-cause detail, or evidence of confidentiality or integrity impact.

Likely exposure

Exposure is likely limited to deployments running Memcached 1.6.0, 1.6.1, or 1.6.2, especially if the service is reachable by untrusted clients or networks.

Exploitation context

The CVE text states remote attackers can cause a crash. KEV is false, and the provided sources do not state active exploitation or public weaponization.

Researcher notes

Evidence is sparse: the bundle names affected versions and crash impact but lacks CVSS, CWE, patch notes, and exploit telemetry. Do not assume impact beyond daemon crash without additional vendor data.

Mitigation direction

  • Upgrade Memcached deployments to 1.6.3 or later.
  • Check the linked Memcached issue and vendor guidance for operational details.
  • Restrict Memcached access to trusted application networks only.
  • Prioritize internet-exposed or business-critical cache nodes first.

Validation and detection

  • Inventory Memcached versions across production and staging.
  • Confirm no instances run 1.6.0 through 1.6.2.
  • Review network exposure for Memcached ports and access paths.
  • Check service monitoring for unexplained Memcached crashes.
Prepared
Confidence
medium
Sources
3

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-2020-22570 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
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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.