# CVE-2023-1256: CVE-2023-1256

> Unauthenticated attackers can remotely read data, cause denial of service, and tamper with alarm states in AVEVA Plant SCADA and Telemetry Server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-22mx-qh6h-fcv2

## What is CVE-2023-1256?

CVE-2023-1256 is a critical missing authorization vulnerability in AVEVA Plant SCADA, published on 16 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2023-1256?

It affects 2 products.


Products: Aveva Aveva Plant Scada, Aveva Telemetry Server.

## How do I fix CVE-2023-1256?

No fix has been published for CVE-2023-1256 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-1256 being exploited?

There is no known exploitation of CVE-2023-1256 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1256 and fix it if it is affected.

What it is: CVE-2023-1256 is a critical missing authorization vulnerability in AVEVA Plant SCADA, published on 16 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1256 in the wild and no public exploit code.

Affected product: AVEVA Plant SCADA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1256/ (Markdown: https://insights.sbomify.com/CVE-2023-1256/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1256
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1256
- OSV: https://osv.dev/vulnerability/CVE-2023-1256

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1256/
Summaries are generated and may contain mistakes; the official description above is the record.