# CVE-2024-6456: SQL Injection vulnerability in AVEVA Historian Server

> An attacker can execute malicious SQL commands via a crafted URL, requiring user interaction, potentially leading to code execution or data access.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Aug 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-h755-c54r-2xq5

## What is CVE-2024-6456?

CVE-2024-6456 is a high-severity SQL injection vulnerability in AVEVA Historian Web Server, published on 15 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

AVEVA Historian Server has a vulnerability, if exploited, could allow a malicious SQL command to execute under the privileges of an interactive Historian REST Interface user who had been socially engineered by a miscreant into opening a specially crafted URL.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-6456?


## How do I fix CVE-2024-6456?

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

## Is CVE-2024-6456 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6456 and fix it if it is affected.

What it is: CVE-2024-6456 is a high-severity SQL injection vulnerability in AVEVA Historian Web Server, published on 15 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6456 in the wild and no public exploit code.

Affected product: AVEVA Historian Web Server. 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-2024-6456/ (Markdown: https://insights.sbomify.com/CVE-2024-6456/index.md)
```

## Sources

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

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