CVE-2021-32996
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 FANUC R-30iA and R-30iB series controllers are vulnerable to integer coercion errors, which cause the device to crash. A restart is required.
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 confidenceFANUC R-30iA and R-30iB series robot controllers contain an integer coercion error vulnerability that can cause the device to crash, requiring a manual restart to restore operation.
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= 7.20= 7.30= 7.40= 7.43= 7.50= 7.63= 7.70= 7.20= 7.30= 7.40= 7.43= 7.50= 7.63= 7.70= 8.10= 8.13= 8.20= 8.23= 8.26= 8.30= 8.33= 8.36= 8.10= 8.13= 8.20= 8.23= 8.26= 8.30= 8.33= 8.36= 8.10= 8.13= 8.20= 8.23= 8.26= 8.30= 8.33= 8.36= 9.10= 9.13= 9.16= 9.30= 9.36= 9.40= 9.10= 9.13= 9.16= 9.30= 9.36= 9.40= 9.10= 9.13= 9.16= 9.30= 9.36= 9.40CVSS 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 controller modelCheck the label on the controller cabinet or access the Teach Pendant to determine if the unit is an R-30iA or R-30iB series (including Mate, Compact, Mate Plus, Compact Plus, or Mini Plus variants)Affected if The controller is any R-30iA or R-30iB series model
-
Retrieve firmware versionOn the Teach Pendant, navigate to the system information or version screen (typically under Menu > System > Version) or access the controller via FTP/SFTP to read the version file if availableAffected if The installed firmware version matches any of the listed affected versions: 7.20, 7.30, 7.40, 7.43, 7.50, 7.63, 7.70 for R-30iA; 8.10, 8.13, 8.20, 8.23, 8.26, 8.30, 8.33, 8.36 for R-30iB; or 9.10, 9.13, 9.16, 9.30, 9.36, 9.40 for R-30iB Plus variants
-
Verify crash conditionTrigger the vulnerable integer coercion condition through the exposed interface or observe if the controller has experienced unexplained crashes requiring manual restartAffected if The device has crashed unexpectedly or the integer coercion vulnerability can be reproducibly triggered
A user is affected if they are running any of the listed firmware versions on an R-30iA or R-30iB series controller and the integer coercion vulnerability is present or has caused crashes.
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 dataContact FANUC for firmware updates addressing this vulnerability and implement network segmentation to isolate industrial controllers from untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32996 — 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-32996 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