LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24055: Verint 5620PTZ Verint_FW_0_42 and Verint 4320 V4320_FW_0_23, and V4320_FW_0_31 units feature an autodiscove...

Verint 5620PTZ Verint_FW_0_42 and Verint 4320 V4320_FW_0_23, and V4320_FW_0_31 units feature an autodiscovery service implemented in the binary executable '/usr/sbin/DM' that listens on port TCP 6666. The service is vulnerable to a stack buffer overflow. It is worth noting that this service does not require any authentication.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some Verint PTZ camera firmware exposes an unauthenticated autodiscovery service on TCP port 6666. The service has a stack buffer overflow, meaning a reachable camera could be disrupted or potentially compromised. The source bundle does not provide CVSS, confirmed exploitation, or a named patch.

Executive priority

Prioritize containment and inventory if these cameras support physical security operations. The business risk is highest when vulnerable devices are reachable beyond a tightly controlled camera network, because the vulnerable service is unauthenticated.

Technical view

CVE-2020-24055 affects Verint 5620PTZ Verint_FW_0_42 and Verint 4320 V4320_FW_0_23/V4320_FW_0_31. The vulnerable component is /usr/sbin/DM, an unauthenticated autodiscovery service listening on TCP 6666. The stated flaw is a stack buffer overflow; exploit mechanics and vendor remediation are not provided.

Likely exposure

Exposure is likely limited to organizations still running the named Verint camera models and firmware, especially where TCP 6666 is reachable from user networks, vendor networks, or the internet. Internet exposure would materially increase urgency.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Because the service requires no authentication and is network-reachable, the issue should be treated as serious where affected devices are accessible.

Researcher notes

Evidence is limited to the CVE description and IOActive references. No CVSS, CWE, exploit status, patch version, or detailed impact statement is included in the bundle. Avoid assuming confirmed remote code execution unless vendor or research detail supports it.

Mitigation direction

  • Check Verint or successor vendor guidance for fixed firmware or replacement options.
  • Block TCP 6666 from untrusted networks and the internet.
  • Place affected cameras on isolated, monitored camera VLANs.
  • Restrict management and discovery traffic to approved administrative hosts.
  • Retire or replace devices if no supported remediation exists.

Validation and detection

  • Inventory Verint 5620PTZ and Verint 4320 units and record firmware versions.
  • Confirm whether TCP 6666 is reachable from any untrusted network segment.
  • Review external exposure scans for affected camera IP addresses.
  • Check firewall rules for unnecessary discovery-service access.
  • Monitor logs or network telemetry for unexpected TCP 6666 connections.
Prepared
Confidence
medium
Sources
4

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-24055 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
3Source links

CVSS and timeline data

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

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.