dbcve.org
Aveva Plant ScadaApplication · Aveva

CVE-2023-1256

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The listed versions of AVEVA Plant SCADA and AVEVA Telemetry Server are vulnerable to an improper authorization exploit which could allow an unauthenticated user to remotely read data, cause denial of service, and tamper with alarm states.

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 confidence

This CVE affects AVEVA Plant SCADA and AVEVA Telemetry Server, where an improper authorization vulnerability allows unauthenticated remote attackers to read sensitive data, cause denial of service, and tamper with alarm states. The critical CVSS score of 9.8 reflects the severity of unauthenticated remote access to industrial control systems.

MitigationApply vendor-supplied patches or updates for the affected AVEVA versions and implement network segmentation to restrict unauthorized access to SCADA systems.

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
Aveva Plant ScadaApplication
Affected:= 2020r2= 2023
Telemetry ServerApplication
Affected:= 2020r2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AVEVA product installation
    Check Windows Programs and Features or list of installed software for AVEVA Plant SCADA or AVEVA Telemetry Server
    Affected if Either product is listed as installed
  2. Identify installed version
    Right-click the installed AVEVA product in Programs and Features, or launch the application and check About/Help menu for version information
    Affected if Version matches 2020r2 or 2023 for Plant SCADA, or 2020r2 for Telemetry Server
  3. Verify network service exposure
    Check Windows services list or firewall rules for AVEVA-related services listening on network ports (commonly TCP ports 5450, 5451, 12345 for SCADA communications)
    Affected if AVEVA network services are running and accessible from network hosts
  4. Check authentication configuration
    Review AVEVA system configuration files or security settings for authentication enforcement on remote access features
    Affected if Remote unauthenticated access is permitted or authentication can be bypassed

You are affected if AVEVA Plant SCADA 2020r2/2023 or AVEVA Telemetry Server 2020r2 is installed with network services exposed and improper authorization configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or updates for the affected AVEVA versions and implement network segmentation to restrict unauthorized access to SCADA systems.

Recommended fix Moderate confidence

AVEVA Plant SCADA 2023 Update 1 or later (latest available patch); AVEVA Telemetry Server latest available version

  1. 1. Identify the currently installed version of AVEVA Plant SCADA or AVEVA Telemetry Server using the product's 'About' or version information feature
  2. 2. Navigate to the AVEVA Customer Portal (customers.aveva.com) or AVEVA Support website to obtain the latest security patches
  3. 3. Download and apply the appropriate security update for your product version - for Plant SCADA 2020r2 and 2023, apply the latest cumulative update; for Telemetry Server 2020r2, apply the latest service pack
  4. 4. After applying the patch, verify the version has been updated and restart affected services
  5. 5. Validate that the authorization controls are functioning correctly by testing access controls
Caveat Review release notes for any configuration or compatibility changes before applying; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aveva Plant Scada Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1256 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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