LiveActive security incident?Get immediate response
CVE Record

CVE-2020-27251: A heap overflow vulnerability exists within FactoryTalk Linx Version 6.11 and prior.

A heap overflow vulnerability exists within FactoryTalk Linx Version 6.11 and prior. This vulnerability could allow a remote, unauthenticated attacker to send malicious port ranges, which could result in remote code execution.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

FactoryTalk Linx 6.11 and earlier has a heap overflow that could let a remote, unauthenticated attacker achieve code execution by sending malicious port ranges. The bundle does not provide CVSS scoring or confirmed exploitation evidence, but unauthenticated remote code execution in an operational technology product is business-significant.

Executive priority

Treat this as a high-priority OT exposure review if FactoryTalk Linx is present. The urgency comes from unauthenticated remote code execution potential, not from confirmed exploitation in the supplied evidence.

Technical view

CVE-2020-27251 is described as CWE-122 heap-based buffer overflow in FactoryTalk Linx 6.11 and prior. The attack condition cited is remote unauthenticated submission of malicious port ranges, with possible remote code execution. No exploit chain, affected deployment prerequisites, or fixed version details are included in the supplied bundle.

Likely exposure

Exposure is likely limited to environments running FactoryTalk Linx version 6.11 or earlier, especially systems reachable over networks where untrusted hosts can interact with the vulnerable service. The supplied sources do not identify specific ports, configurations, or downstream products.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described impact is still serious because the vulnerability is remote and unauthenticated, with potential code execution from crafted port-range input.

Researcher notes

Evidence is sparse in the supplied bundle. Avoid assuming exploit availability, exact ports, or a specific fixed version without the referenced advisory or vendor bulletin. Focus validation on version inventory, reachability, and vendor-confirmed remediation.

Mitigation direction

  • Identify all FactoryTalk Linx deployments and record installed versions.
  • Prioritize FactoryTalk Linx 6.11 and earlier for remediation review.
  • Check CISA and vendor guidance for fixed releases or approved mitigations.
  • Restrict network access to FactoryTalk Linx from untrusted systems.
  • Apply OT change control before updates in production environments.

Validation and detection

  • Confirm whether FactoryTalk Linx is installed on OT and engineering workstations.
  • Verify installed versions against the affected range: 6.11 and prior.
  • Review network paths that can reach the FactoryTalk Linx service.
  • Check vendor or CISA advisory status for remediation instructions.
  • Document compensating controls if patching cannot occur immediately.
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.

cwe · low confidence lookup

CWE-122: 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-27251 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aFactoryTalk LinxVersion 6.11 and priorListed
Weakness

CWE details

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

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

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