CVE-2021-33008
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 · uneditedAVEVA System Platform versions 2017 through 2020 R2 P01 does not perform any authentication for functionality that requires a provable user identity.
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 · high confidenceAVEVA System Platform versions 2017 through 2020 R2 P01 contains an authentication bypass vulnerability where certain functions that should require provable user identity can be accessed without any authentication. An unauthenticated remote attacker can exploit this to access sensitive functionality within the SCADA/ICS platform.
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>= 2017, < 2020= 2020CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify AVEVA System Platform versionLocate the installed version through the product's About dialog, registry keys, or installation directories. Check HKEY_LOCAL_MACHINE\SOFTWARE\AVEVA in Windows Registry or look in the installation folder for version information.Affected if The installed version is 2017, 2018, 2019, 2020, or any version from 2017 through 2020 R2 P01 that is not patched.
-
Confirm the 2020 version is affectedIf the version displays as exactly 2020 (without a patch level designator like R2 P01), it is within the affected range.Affected if Version is 2020 without the patched release designation.
-
Verify version 2017 through 2019 are affectedAny installation from 2017, 2018, or 2019 product releases falls within the vulnerable range.Affected if Version is 2017, 2018, or 2019 (any sub-release).
-
Assess network exposure of SCADA interfaceDetermine if the AVEVA System Platform web interfaces, XML APIs, or SCADA communication ports are accessible from networks outside the trusted operational zone.Affected if The SCADA platform is directly accessible from external or untrusted networks without firewall filtering.
If the installed AVEVA System Platform version is 2017 through 2020 (any release) and the interface is network-accessible, the environment is affected by this authentication bypass vulnerability.
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 data2020
Apply the vendor patch or upgrade to a patched version of AVEVA System Platform. If patching is immediately infeasible, implement network segmentation and restrict external access to the affected system as compensating controls.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33008 — 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-33008 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