VulnerabilityPublished 15 Oct 2024Updated 4 Nov 2025

CVE-2024-47945: The devices are vulnerable to session hijacking due to insufficient entropy in its session ID

Source GCVE Database

Compare

Authoritative record:CVE-2024-47945· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical.

Data as of 30 Oct 2026, 02:01 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	9.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3qfw-5g24-8pmq

What to do

AI-suggested

Since the vulnerability stems from weak session ID generation, remediation requires updating the session ID generation mechanism to use a cryptographically secure random number generator with proper seeding. Until a fix is available, affected devices should consider additional protective measures such as session timeout enforcement and monitoring for suspicious session activity.

Description

This vulnerability involves predictable session IDs generated with insufficient entropy due to improper use of the rand() function and missing srand() initialization. The limited session ID space (32,768 values per user) enables attackers to pre-generate valid session IDs and hijack user sessions, leading to unauthorized access. The flaw affects certain devices but no specific versions or patches are provided.

Impact

Successful exploitation allows attackers to hijack user sessions by predicting session IDs, leading to unauthorized access to user accounts and sensitive information. The vulnerability compromises confidentiality and integrity but does not affect availability. No known exploits are reported in the wild.

Summary

CVE-2024-47945 describes a session hijacking vulnerability caused by weak session ID generation. The session IDs are generated using an insecure rand() function without proper seeding via srand(), resulting in only 32,768 possible session ID values per user. This predictability allows attackers to precompute valid session IDs and gain unauthorized access to user sessions. The vulnerability is classified under CWE-331 (Insufficient Entropy) and CWE-340 (Insufficiently Random Values). The CVSS v3.1 score is 9.1 (critical), reflecting network attack vector, low complexity, no privileges or user interaction required, and high confidentiality and integrity impact.

CWE-331Insufficient Entropy (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
Implementation
Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.
OWASP Cheat Sheets
Session Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.2 (opens in a new tab)
V3.2.4 (opens in a new tab)
V2.3.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-340Generation of Predictable Numbers or Identifiers (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a scheme that generates numbers or identifiers that are more predictable than required.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 02:01 UTC

WeaknessesCWE-331, CWE-340

Technical details

References

Community reviews

Related threats