# CVE-2024-45751: Weak cryptography in n/a

> tgt uses a predictable PRNG seed, allowing attackers to predict challenge sequences and bypass authentication mechanisms.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2024
- **Updated:** 30 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-45751, DLA-3976-1, GHSA-cwq5-xwx7-85wm, MGASA-2024-0304, OESA-2024-2156, SUSE-SU-2025:02591-1, SUSE-SU-2025:02740-1, UBUNTU-CVE-2024-45751, USN-7024-1, USN-8325-1

## What is CVE-2024-45751?

CVE-2024-45751 is a medium-severity vulnerability in n/a, published on 6 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tgt (aka Linux target framework) before 1.0.93 attempts to achieve entropy by calling rand without srand. The PRNG seed is always 1, and thus the sequence of challenges is always identical.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tgt` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.0.85-150600.10.3.1 |
| `tgt` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.0.85-150600.10.3.1 |
| `tgt` | openSUSE:Leap 15.6 | All versions | 1.0.85-150600.10.3.1 |

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

Upgrade to a fixed version.

## Is CVE-2024-45751 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45751 is a medium-severity vulnerability in n/a, published on 6 Sep 2024. 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-2024-45751 in the wild and no public exploit code.

Affected product: n/a. 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-45751/ (Markdown: https://insights.sbomify.com/CVE-2024-45751/index.md)
```

## Sources

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

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