CVE-2019-6832
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 · uneditedA CWE-287: Authentication vulnerability exists in spaceLYnk (all versions before 2.4.0) and Wiser for KNX (all versions before 2.4.0 - formerly known as homeLYnk), which could cause loss of control when an attacker bypasses the authentication.
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 confidenceAuthentication bypass vulnerability (CWE-287) in spaceLYnk and Wiser for KNX building automation controllers allows unauthenticated attackers to bypass authentication mechanisms and gain control of the system. The vulnerability affects all versions prior to 2.4.0.
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.4.0< 2.4.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
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.
-
Identify installed building automation controllersLocate Schneider Electric spaceLYnk or Wiser for KNX devices on your network or in your physical inventory. Check network scans, device inventories, or physical asset lists for these specific product names.Affected if Either product is present in the environment
-
Determine the firmware versionAccess the device's web management interface or use the device's built-in version check feature (typically found in System > Information or About sections) to retrieve the currently installed firmware version.Affected if The firmware version cannot be determined or is unknown
-
Compare version against vulnerable rangeCompare the identified firmware version number to the affected range: any version prior to 2.4.0 (for example, 2.3.x, 2.2.x, 2.1.x, 2.0.x, 1.x). Note that version 2.4.0 and later are NOT affected.Affected if The installed version is less than 2.4.0 (for example, 2.3.1, 2.2.0, or 1.9.5)
-
Verify network accessibility of management interfaceDetermine if the device's web management interface (typically HTTP/HTTPS on ports 80 or 443) is accessible from untrusted networks, the internet, or network segments outside the building automation network.Affected if The management interface is exposed to untrusted networks and the firmware version is below 2.4.0
You are affected if Schneider Electric spaceLYnk or Wiser for KNX with firmware version prior to 2.4.0 is present and its management interface is network-accessible.
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 data2.4.0
Upgrade spaceLYnk and Wiser for KNX to version 2.4.0 or later to incorporate the authentication fix. If immediate upgrade is not possible, restrict network access to these devices and monitor for unauthorized access attempts.
- Consultation8.0 h
- Implementation4.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 $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6832 — 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-2019-6832 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