dbcve.org
Sitemanager 1129 FirmwareOperating system · Secomea

CVE-2021-32010

HIGH · 8.1 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to 9.7.622134021 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Inadequate encryption strength in the TLS stack allows man-in-the-middle attacks. The vulnerability stems from support for weak cipher suites or outdated TLS protocols in Secomea SiteManager, LinkManager, and GateManager prior to version 9.7, enabling attackers to intercept or manipulate encrypted communications.

MitigationUpgrade Secomea SiteManager, LinkManager, and GateManager to version 9.7 or later to remediate the weak TLS encryption. After upgrading, verify that only strong cipher suites and current TLS protocols are enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sitemanager 1129 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 1139 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 1149 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3329 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3339 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3349 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3529 FirmwareOperating system
Affected:< 9.7.622134021
Sitemanager 3539 FirmwareOperating system
Affected:< 9.7.622134021

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the SiteManager model number
    Locate the model identifier on the device label, web interface dashboard, or system status page. The affected models are 1129, 1139, 1149, 3329, 3339, 3349, 3529, and 3539.
    Affected if The device is one of these model numbers.
  2. Determine the installed firmware version
    Access the Secomea SiteManager web interface and navigate to the System Status or About page to view the firmware version. Alternatively, use the CLI command 'version' or 'show system info' if available.
    Affected if The firmware version is below 9.7.622134021.
  3. Check TLS protocol configuration
    Access the SiteManager SSL/TLS settings through the web interface under Security or Network configuration. Verify which TLS protocol versions are enabled (TLS 1.0, TLS 1.1, or TLS 1.2).
    Affected if TLS 1.0 or TLS 1.1 is enabled.
  4. Check cipher suite configuration
    Navigate to the SSL/TLS cipher configuration section in the web interface. Review the list of enabled cipher suites for presence of weak or export-grade ciphers (such as RC4, 3DES, or NULL encryption).
    Affected if Weak cipher suites are enabled or the configuration allows legacy ciphers.

A user is affected if they run a SiteManager model 1129/1139/1149/3329/3339/3349/3529/3539 with firmware below 9.7.622134021 and have weak TLS protocols or cipher suites enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.7.622134021 or later
Fixed in 9.7.622134021
Interim mitigation

Upgrade Secomea SiteManager, LinkManager, and GateManager to version 9.7 or later to remediate the weak TLS encryption. After upgrading, verify that only strong cipher suites and current TLS protocols are enabled.

Recommended fix Moderate confidence

Firmware version 9.7.622134021 or later

  1. Identify the current SiteManager model number and firmware version installed
  2. Navigate to the Secomea support portal or contact Secomea directly to obtain the fixed firmware version 9.7.622134021 or later
  3. Follow Secomea's standard firmware upgrade procedure for your SiteManager model
  4. After upgrade, verify the TLS configuration uses strong cipher suites and that the firmware version is 9.7.622134021 or higher
  5. Test TLS connectivity to confirm the man-in-the-middle vulnerability is remediated
Caveat Review release notes for any configuration changes required when upgrading to version 9.7

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sitemanager 1129 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data