LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32010: Clients may connect to a GateManager with TLS 1.0

Inadequate Encryption Strength vulnerability in TLS stack of Secomea SiteManager, LinkManager, GateManager may facilitate man in the middle attacks. This issue affects: Secomea SiteManager All versions prior to 9.7. Secomea LinkManager versions prior to 9.7. Secomea GateManager versions prior to 9.7.

MediumCVSS 5.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability means older Secomea remote access components may allow clients to connect using TLS 1.0, an outdated encryption protocol. That can weaken confidentiality and integrity if an attacker can position themselves between the client and GateManager. The issue is medium severity and requires a difficult network position, but it matters for operational technology remote access paths.

Executive priority

Treat this as a targeted operational technology remote access hygiene issue, not an emergency. Prioritize remediation for internet-facing or third-party remote access deployments, because compromised connection security could affect sensitive operational environments.

Technical view

CVE-2021-32010 is an inadequate encryption strength issue in the TLS stack of Secomea SiteManager, LinkManager, and GateManager before version 9.7. The CVSS 3.1 score is 5.6 with network attack vector, high complexity, no privileges, no user interaction, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where Secomea SiteManager, LinkManager, or GateManager versions before 9.7 are used for remote access, especially across untrusted networks. The source bundle does not identify specific deployment defaults, internet exposure prevalence, or affected CPEs.

Exploitation context

The CVE describes potential man-in-the-middle attacks enabled by TLS 1.0 support. The source bundle does not state active exploitation, public exploit availability, or inclusion in CISA KEV. Attack feasibility depends on network positioning and client connection behavior.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, affected version threshold, CWE-326, and Secomea advisory reference. The bundle does not provide protocol traces, configuration details, exploit confirmation, or separate fixed-build notes beyond the pre-9.7 affected range.

Mitigation direction

  • Inventory Secomea SiteManager, LinkManager, and GateManager versions.
  • Prioritize upgrade or replacement of affected components below version 9.7.
  • Review Secomea’s advisory for product-specific remediation guidance.
  • Disable TLS 1.0 where vendor-supported configuration allows it.
  • Restrict remote access paths to trusted networks until remediated.

Validation and detection

  • Confirm deployed Secomea component versions are 9.7 or later.
  • Check whether GateManager endpoints still accept TLS 1.0.
  • Review remote access architecture for man-in-the-middle exposure paths.
  • Verify compensating controls limit untrusted network interception opportunities.
  • Document remediation status for each SiteManager, LinkManager, and GateManager instance.
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-326: 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
cve · low confidence lookup

CVE-2021-32010 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
Medium
CVSS
5.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

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
2Source 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
5.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L2.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.6Medium
CVSS 3.1 vector shape for CVE-2021-32010Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

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
SecomeaSiteManagerAllListed
SecomeaLinkManagerunspecifiedListed
SecomeaGateManagerunspecifiedListed
Weakness

CWE details

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

CWE-326 · source CWE mapping

Inadequate Encryption Strength

Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.