CVE-2021-22733
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 · uneditedImproper Privilege Management vulnerability exists in homeLYnk (Wiser For KNX) and spaceLYnk V2.60 and prior which could cause shell access when unauthorized code is loaded into the system folder.
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 confidenceImproper privilege management in homeLYnk (Wiser For KNX) and spaceLYnk V2.60 and prior allows unauthenticated or low-privilege attackers to place unauthorized code in the system folder, which is then executed with elevated privileges, resulting in shell access to the device.
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<= 2.6.0<= 2.6.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed firmware versionAccess the device web interface or use the device's administrative console to view the firmware version. For web interface, typically navigate to Settings > About or similar. For CLI, check available commands or documentation for version display.Affected if The firmware version is 2.6.0 or earlier (any version <= 2.6.0).
-
Identify device modelConfirm whether the device is a Schneider Electric spaceLYnk or homeLYnk controller by checking the device label, web interface header, or administrative console.Affected if The device is a spaceLYnk or homeLYnk with firmware <= 2.6.0.
-
Inspect system folder for unauthorized filesExamine the system folder or system directory on the device for any unexpected files, scripts, or executables that were not installed by the administrator. Use file system listing commands available on the device or via administrative interface.Affected if Unexpected or unauthorized files are present in the system directory, indicating potential exploitation.
-
Check for unauthorized elevated processes or shellsReview running processes on the device. Look for shell processes or command interpreters (such as /bin/sh, /bin/bash) running under elevated privileges that are not part of legitimate system operations.Affected if Shell processes or unexpected executables are running with elevated (root or administrator) privileges.
-
Review user accounts and privilege configurationCheck the device user management interface or configuration for unauthorized accounts, especially any low-privilege or unauthenticated accounts that should not exist, or accounts with unexpected elevated permissions.Affected if Unauthorized user accounts exist or privilege misconfigurations are found.
The environment is affected if the device is a Schneider Electric spaceLYnk or homeLYnk running firmware version 2.6.0 or earlier.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to V2.61 or later which addresses the privilege management flaw; if upgrading is not possible, restrict network access to the device and monitor for unauthorized file placement in system directories.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-22733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22733 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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