CVE-2021-22276
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 · uneditedThe vulnerability allows a successful attacker to bypass the integrity check of FW uploaded to the free@home System Access Point.
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 confidenceThe vulnerability in the free@home System Access Point allows attackers to bypass the firmware integrity check mechanism during the FW upload process, potentially enabling installation of modified or malicious firmware on 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.4< 2.6.4< 2.6.4< 2.6.4< 2.6.4CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 the System Access Point modelLocate the physical device or check the device documentation/web interface to determine the exact model: System Access Point 2.0, System Access Point 127v, Wl System Access Point 127v, Wl System Access Point, or Wl System Access Point 2.0Affected if The model is any of the listed affected products
-
Access the device firmware versionLog into the free@home System Access Point web interface or API and navigate to the device settings or system information page to retrieve the current firmware versionAffected if Unable to retrieve firmware version for verification
-
Compare installed version against vulnerable rangeCheck if the installed firmware version is less than 2.6.4. Compare your version number to the threshold: versions 2.6.3, 2.6.2, 2.6.1, 2.5.x and earlier are all in the vulnerable rangeAffected if Firmware version is less than 2.6.4 (for example, 2.6.3, 2.5.0, etc.)
-
Verify firmware integrity check statusDuring a firmware upload attempt, observe whether the system performs cryptographic verification of the firmware file before installation beginsAffected if Firmware installs without proper integrity verification or accepts modified firmware files
You are affected if your ABB free@home System Access Point runs firmware version lower than 2.6.4 and the device allows firmware installation without proper cryptographic integrity checks.
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.
dbcve · scoped2.6.4
Apply vendor patches to ensure proper cryptographic verification of firmware integrity before allowing installation on the System Access Point.
Firmware version 2.6.4
- Download the System Access Point firmware version 2.6.4 or later from the official ABB support portal (search.abb.com)
- Access the free@home System Access Point web interface using administrative credentials
- Navigate to the firmware update section in the device settings
- Upload the firmware version 2.6.4 file
- Confirm the firmware upgrade and allow the device to reboot
- Verify the device is running firmware version 2.6.4 or later after the reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22276 — 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-22276 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