tgt up to 1.0.92 entropy

Summaryinfo

A vulnerability classified as problematic was found in tgt up to 1.0.92. Affected is an unknown function. Executing a manipulation can lead to entropy. This vulnerability is tracked as CVE-2024-45751. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in tgt up to 1.0.92 and classified as problematic. This vulnerability affects an unknown function. The manipulation with an unknown input leads to a entropy vulnerability. The CWE definition for the vulnerability is CWE-332. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. As an impact it is known to affect confidentiality. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability was named CVE-2024-45751 since 09/06/2024. The exploitation appears to be difficult. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.

The vulnerability scanner Nessus provides a plugin with the ID 211974 (Debian dla-3976 : tgt - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.0.93 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (211974). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• tgt

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9
• 1.0.10
• 1.0.11
• 1.0.12
• 1.0.13
• 1.0.14
• 1.0.15
• 1.0.16
• 1.0.17
• 1.0.18
• 1.0.19
• 1.0.20
• 1.0.21
• 1.0.22
• 1.0.23
• 1.0.24
• 1.0.25
• 1.0.26
• 1.0.27
• 1.0.28
• 1.0.29
• 1.0.30
• 1.0.31
• 1.0.32
• 1.0.33
• 1.0.34
• 1.0.35
• 1.0.36
• 1.0.37
• 1.0.38
• 1.0.39
• 1.0.40
• 1.0.41
• 1.0.42
• 1.0.43
• 1.0.44
• 1.0.45
• 1.0.46
• 1.0.47
• 1.0.48
• 1.0.49
• 1.0.50
• 1.0.51
• 1.0.52
• 1.0.53
• 1.0.54
• 1.0.55
• 1.0.56
• 1.0.57
• 1.0.58
• 1.0.59
• 1.0.60
• 1.0.61
• 1.0.62
• 1.0.63
• 1.0.64
• 1.0.65
• 1.0.66
• 1.0.67
• 1.0.68
• 1.0.69
• 1.0.70
• 1.0.71
• 1.0.72
• 1.0.73
• 1.0.74
• 1.0.75
• 1.0.76
• 1.0.77
• 1.0.78
• 1.0.79
• 1.0.80
• 1.0.81
• 1.0.82
• 1.0.83
• 1.0.84
• 1.0.85
• 1.0.86
• 1.0.87
• 1.0.88
• 1.0.89
• 1.0.90
• 1.0.91
• 1.0.92

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion