AVEVA System Platform Missing Authentication for Critical Function

published 2022-04-04 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-19729

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits: 0; none known

AVEVA System Platform versions 2017 through 2020 R2 P01 does not perform any authentication for functionality that requires a provable user identity.

Patch / fix

fixed in 1

aveva system_platform 2020

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-21-180-05 updated 2021-07-27 cvss 8.8

AVEVA System Platform (Update A)

AVEVA Software, LLC AVEVA System Platform >= 2017, <= 2020 R2 P01
affected: mitigation “AVEVA recommends organizations evaluate the impact of these vulnerabilities based on their operational environment, architecture, and product implementation.” softwaresupportsp.aveva.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 18 mo ago (2025-04-16)

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

AVEVA AVEVA System Platform

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality

References

aveva.com /content/dam/aveva/documents/support/cyber-security-updates/SecurityBulletin_AVEVA-2021-002.pdf
vendor-advisory
cisa.gov /uscert/ics/advisories/icsa-21-180-05
third-party-advisory, us-government-resource

Sources

CVE List CVE-2021-33008
NVD CVE-2021-33008

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary