CVE-2021-22288
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 Input Validation vulnerability in the ABB SPIET800 and PNI800 module allows an attacker to cause the denial of service or make the module unresponsive.
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 ABB SPIET800 and PNI800 modules contain an improper input validation flaw that allows remote attackers to send specially crafted network requests causing the modules to become unresponsive or crash, resulting in denial of service conditions.
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<= a_b<= a_bCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify if ABB PNI800 or SPIET800 modules are presentLocate and inventory industrial control devices on the network. Consult device documentation, network scans, or physical device labels to confirm the exact model numbers of ABB power meter or communication modules.Affected if Neither ABB PNI800 nor SPIET800 modules are present in the environment.
-
Determine the firmware version of the ABB moduleAccess the device web interface, use the vendor management software, or consult the device status page to retrieve the installed firmware version. Compare this version against the affected version range provided by ABB.Affected if The installed firmware version is at or below the affected version (the specific threshold published by ABB).
-
Verify network accessibility of the affected deviceConfirm whether the device management interface or the network service ports are reachable from network segments that contain untrusted or external systems. Use network scanning tools to identify exposed IP addresses and open ports associated with the module.Affected if The device is directly accessible from untrusted networks without firewall protection or access controls.
-
Check for signs of device instability or unresponsivenessMonitor the device via SNMP, vendor management tools, or periodic ping/connectivity tests. Look for reports of the module becoming unresponsive or requiring restart, which may indicate exploitation attempts.Affected if The device exhibits frequent crashes, unresponsiveness, or requires manual restarts without known cause.
You are affected if you have an ABB PNI800 or SPIET800 module running firmware at or below the vulnerable version threshold and the device is accessible from network segments where untrusted attackers could send crafted requests.
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 dataApply available firmware updates from ABB; until patches are available, implement network segmentation and restrict access to these industrial devices using firewalls or access control lists to limit exposure to untrusted networks.
- 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-22288 — 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-22288 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