VulnerabilityPublished 22 Nov 2024Updated 26 Nov 2024

CVE-2024-5716: Logsign Unified SecOps Platform · Improper Restriction of Excessive Authentication Attempts

Affects Logsign Unified SecOps PlatformSource CVE Database V5

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score

8.6High

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

EPSS: 1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.

What to do

Affected software

Product	Affected	Fixed in
Logsign Unified SecOps Platform	Affected =6.4.6	Fixed in–

AI-suggested

Organizations should immediately implement compensating controls such as restricting network access to the Logsign Unified SecOps Platform to trusted IP addresses or VPNs to reduce exposure. Monitoring and alerting on unusual password reset activity can help detect exploitation attempts. Administrators should enforce strong password policies and consider multi-factor authentication (MFA) where possible to mitigate unauthorized access risks. Until an official patch is released, consider disabling or restricting the password reset functionality if feasible. Regularly audit user accounts and access logs for suspicious activity. Engage with Logsign support or security advisories to obtain updates on patches or mitigations. Additionally, segment the platform within the network to limit potential lateral movement if compromised. Employ intrusion detection systems to monitor for anomalous authentication bypass attempts targeting this vulnerability.

Description

Logsign Unified SecOps Platform Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of Logsign Unified SecOps Platform. Authentication is not required to exploit this vulnerability. The specific flaw exists within the password reset mechanism. The issue results from the lack of restriction of excessive authentication attempts. An attacker can leverage this vulnerability to reset a user's password and bypass authentication on the system. Was ZDI-CAN-24164.

Impact

The vulnerability allows attackers to bypass authentication and gain unauthorized access to the Logsign Unified SecOps Platform, potentially compromising sensitive security monitoring data and operational controls. This can lead to unauthorized data disclosure (confidentiality impact), unauthorized changes to system configurations or logs (integrity impact), and potential disruption or denial of security services (availability impact). Since the platform is often integrated into enterprise security operations, exploitation could undermine an organization's entire security posture, enabling further lateral movement or persistence by attackers. The lack of authentication requirement and ease of exploitation increase the likelihood of attacks, especially in environments where this platform is exposed to untrusted networks. Organizations relying on this platform for incident detection and response may face delayed or impaired security operations, increasing overall risk exposure.

CWE-307Improper Restriction of Excessive Authentication Attempts (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
Architecture and Design
Common protection mechanisms include: Disconnecting the user after a small number of failed attempts; Implementing a timeout; Locking out a targeted account; Requiring a computational task on the user's part.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authentication (opens in a new tab)
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP ASVS 4.0.3
V2.2.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Password Spraying (opens in a new tab)
Credential Stuffing (opens in a new tab)
Use of Known Kerberos Credentials (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

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 00:43 UTC

WeaknessesCWE-307

Technical details

References

Community reviews

Related threats