dbcve.org
Spacelynk FirmwareOperating system · Schneider Electric

CVE-2021-22737

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-26
Fix available
A fix is available. Upgrade to after 2.6.0 or later.
See remediation →
100/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
Insufficiently Protected Credentials vulnerability exists in homeLYnk (Wiser For KNX) and spaceLYnk V2.60 and prior that could cause unauthorized access of when credentials are discovered after a brute force attack.

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 · moderate confidence

Insufficiently protected credentials in homeLYnk and spaceLYnk (Wiser For KNX) V2.60 and prior allow attackers to discover credentials through brute force attacks, enabling unauthorized access to the system.

MitigationImplement secure credential storage using strong hashing algorithms (bcrypt/Argon2), enforce strong password policies, and implement account lockout or rate limiting to prevent brute force attacks.

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
Spacelynk FirmwareOperating system
Affected:<= 2.6.0
Homelynk FirmwareOperating system
Affected:<= 2.6.0

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 device firmware version via web interface
    Log into the Spacelynk or Homelynk web administration panel and navigate to Settings, About, or System Information to locate the firmware version displayed.
    Affected if The displayed firmware version is 2.6.0 or any version prior to 2.6.0 (such as 2.5.x, 2.4.x, etc.)
  2. Verify the exact firmware build number
    Check if there is a build number or revision displayed in the same About/System Information section; some versions may show detailed version like 2.6.0-rc1 or 2.6.0-beta.
    Affected if The firmware version string contains 2.6.0 or a lower minor version number.
  3. Confirm device model is Spacelynk or Homelynk
    Identify the device model through the web interface login page, admin dashboard, or network device discovery (e.g., using nmap or similar to check HTTP response headers or favicon).
    Affected if The device is identified as Schneider Electric Spacelynk or Homelynk and runs the affected firmware version.

A user is affected if their Spacelynk or Homelynk device runs firmware version 2.6.0 or any prior version, as the insufficiently protected credentials in those versions are vulnerable to brute force attacks.

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 a release after 2.6.0
Interim mitigation

Implement secure credential storage using strong hashing algorithms (bcrypt/Argon2), enforce strong password policies, and implement account lockout or rate limiting to prevent brute force attacks.

Recommended fix Moderate confidence

Firmware version newer than 2.6.0 (contact Schneider Electric for exact fixed release)

  1. 1. Identify the current firmware version of the affected Spacelynk or Homelynk device through the device's web interface or administrative panel
  2. 2. Navigate to the Schneider Electric download portal at download.schneider-electric.com
  3. 3. Locate the firmware download section for Spacelynk or Homelynk (depending on your device)
  4. 4. Download the latest available firmware version that is newer than 2.6.0
  5. 5. Review the firmware release notes to confirm the version includes security fixes for CVE-2021-22737
  6. 6. Back up the current device configuration before performing the firmware update
  7. 7. Upload and install the new firmware following the manufacturer's documented upgrade procedure
  8. 8. After upgrade, verify the device is functioning correctly and the new firmware version is installed
Caveat Review release notes for any configuration or feature changes between versions

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

Fix this in Spacelynk Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22737 — 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-22737 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