LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29032: Add integrity check of GateManager firmware

Upload of Code Without Integrity Check vulnerability in firmware archive of Secomea GateManager allows authenticated attacker to execute malicious code on server. This issue affects: Secomea GateManager all versions prior to 9.4.621054022

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Secomea GateManager before 9.4.621054022 could accept a firmware archive without adequate integrity checking. An authenticated attacker could use that weakness to run malicious code on the GateManager server. The business concern is high because GateManager often supports remote access operations, and compromise could affect confidentiality, integrity, and availability.

Executive priority

Treat as high priority for any organization relying on GateManager for remote access or operational connectivity. The required privileges reduce casual exposure, but server-side code execution on a remote access platform can create serious operational and security risk.

Technical view

CVE-2020-29032 is CWE-494: upload of code without integrity check in the GateManager firmware archive process. Public data lists Secomea GateManager all versions prior to 9.4.621054022 as affected. CVSS 3.1 is 8.4 with network attack vector, low complexity, high privileges, user interaction, changed scope, and high CIA impact.

Likely exposure

Exposure is most likely in environments running Secomea GateManager versions older than 9.4.621054022, especially where authenticated users can access firmware archive upload or update functions. The provided sources do not quantify internet exposure or name additional affected products.

Exploitation context

The CVE is not marked as CISA KEV in the supplied bundle, and the sources do not report active exploitation. The attack requires authentication and user interaction, but successful exploitation could execute malicious code on the GateManager server.

Researcher notes

Evidence is sufficient for affected product, version boundary, weakness class, and impact. Evidence is incomplete for real-world exploitation, detailed exploit preconditions beyond CVSS, and compensating controls. Validate through version review and authorized telemetry, not offensive reproduction.

Mitigation direction

  • Inventory all Secomea GateManager instances and record exact versions.
  • Upgrade affected GateManager deployments to 9.4.621054022 or later, per vendor boundary.
  • Review Secomea’s cybersecurity advisory before maintenance windows.
  • Restrict GateManager administrative access to trusted users and networks.
  • Review recent firmware archive upload activity for unexpected changes.

Validation and detection

  • Confirm no GateManager instance is older than 9.4.621054022.
  • Verify administrative accounts with firmware update access are expected and current.
  • Check logs for unusual firmware archive uploads or server-side changes.
  • Confirm update procedures follow current Secomea vendor guidance.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-494: 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-2020-29032 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
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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
3Source 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
8.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H1.76Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2020-29032Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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
SecomeaGateManagerallListed
Weakness

CWE details

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

CWE-494 · source CWE mapping

Download of Code Without Integrity Check

Download of Code Without Integrity Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.