LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37159: Cuckoo Clock 5.0 - Buffer Overflow

Parallaxis Cuckoo Clock 5.0 contains a buffer overflow vulnerability that allows attackers to execute arbitrary code by overwriting memory registers in the alarm scheduling feature. Attackers can craft a malicious payload exceeding 260 bytes to overwrite EIP and EBP, enabling shellcode execution with potential remote code execution.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Parallaxis Cuckoo Clock 5.0 has a critical memory corruption flaw in its alarm scheduling feature. If reachable, an unauthenticated attacker could potentially run code on the affected system. The available sources do not identify a vendor patch, so exposure should be quickly inventoried and reduced.

Executive priority

Treat as urgent for any environment where Cuckoo Clock 5.0 is installed. Because code execution is possible and no fix is cited, prioritize removal, isolation, or replacement over routine patch cycles.

Technical view

CVE-2020-37159 is a stack-based buffer overflow (CWE-121) in Parallaxis Cuckoo Clock 5.0 alarm scheduling. The listed CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impacts.

Likely exposure

Exposure appears limited to systems running Parallaxis Cuckoo Clock version 5.0. Business risk depends on whether the application is installed, network-reachable, and used in an environment with sensitive access or privileges.

Exploitation context

The source bundle references an ExploitDB entry, so public exploit information exists. The bundle states KEV is false, and no cited source confirms active exploitation in the wild.

Researcher notes

The evidence identifies a single affected product and version: Parallaxis Cuckoo Clock 5.0. The vulnerability is described as a stack buffer overflow in alarm scheduling. Provided sources do not include vendor remediation details or confirmed exploitation telemetry.

Mitigation direction

  • Inventory endpoints for Parallaxis Cuckoo Clock 5.0 and remove it where not business-essential.
  • No vendor fix is identified in provided sources; check vendor or distributor guidance.
  • Restrict network exposure and untrusted input paths to the application where removal is not possible.
  • Run the application with least privilege and isolate affected hosts.
  • Prioritize replacement if no supported patched version is available.

Validation and detection

  • Search software inventory for Parallaxis Cuckoo Clock version 5.0.
  • Review endpoint telemetry for the application executable and unexpected child processes.
  • Confirm whether alarm scheduling functionality is enabled or reachable in deployed use.
  • Check vendor, CVE, VulnCheck, and ExploitDB references for updated remediation information.
  • Document compensating controls on any host where the software remains installed.
Prepared
Confidence
medium
Sources
5

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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-37159 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
4Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-37159Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
ParallaxisCuckoo Clock5.0Listed
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.