CVE-2024-45751

What it actually does

The tgt framework calls rand without a preceding srand, leaving the PRNG seeded at 1 and producing an identical deterministic sequence of challenges on every invocation.

Why it matters to the business

Predictable challenges in iSCSI target implementations can allow attackers to bypass integrity or authentication checks, risking unauthorized storage access or data tampering in environments using Nomad or tgt.

How an attack unfolds

An attacker connects to an affected target, receives the fixed challenge sequence generated from seed 1, precomputes valid responses offline, and supplies them to complete authentication or validation steps that should have been unpredictable.

How to fix it

Upgrade github.com/hashicorp/nomad to 1.5.1 or later and fujita/tgt to commit 0b080d7df9aca0df2eb99c81b383c73b1a200325 or later; rebuild and redeploy any dependent packages.

How to confirm the fix worked

Confirm deployed versions match or exceed the listed fixed releases; restart the service multiple times and verify that generated challenges differ between runs.

Typical attack path

1. Locate publicly reachable tgt or Nomad iSCSI endpoints
2. Establish a session to trigger challenge generation
3. Capture the deterministic challenge values
4. Reproduce the PRNG sequence locally using the known seed
5. Submit precomputed responses to bypass security controls

How to detect it

Review iSCSI target logs for repeated identical challenge sequences across separate connections or restarts; correlate with connection timestamps to identify anomalous session patterns.

What your security team should do

• Apply the listed version upgrades immediately on all Nomad and tgt deployments
• Scan package manifests for downstream consumers of the affected libraries
• Add version pinning and automated dependency checks to build pipelines