# CVE-2024-5264: Network Key Transfer with AES KHT vulnerability in Luna EFT

> Administrative users can access backups via offline analysis due to weak cryptographic implementation in Thales Luna EFT.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hxp2-c3hq-rcq5

## What is CVE-2024-5264?

CVE-2024-5264 is a medium-severity vulnerability in Thales Luna EFT, published on 23 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Network Transfer with AES KHT in Thales Luna EFT 2.1 and above allows a user with administrative console access to access backups taken via offline analysis

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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

It affects 1 product.


Products: Thalesgroup Luna Eft.

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

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

## Is CVE-2024-5264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5264 is a medium-severity vulnerability in Thales Luna EFT, published on 23 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5264 in the wild and no public exploit code.

Affected product: Thales Luna EFT. 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-5264/ (Markdown: https://insights.sbomify.com/CVE-2024-5264/index.md)
```

## Sources

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

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