VulnerabilityPublished 9 Oct 2024Updated 10 Oct 2024

CVE-2024-48942: Improper Control of Interaction Frequency

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

9.1Critical

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

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

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 9 Oct 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

AI-suggested

To mitigate CVE-2024-48942, organizations should take the following specific actions: 1) Immediately audit the usage of the Syracom Secure Login 2FA plugin across all Atlassian Jira, Confluence, and Bitbucket instances and identify affected versions up to 3.1.4.5. 2) If possible, disable the vulnerable 2FA plugin temporarily or restrict access to the /plugins/servlet/twofactor/public/pinvalidation endpoint via network controls such as firewalls or reverse proxies to limit exposure. 3) Implement additional rate limiting and monitoring on the 2FA validation endpoint to detect and block brute-force attempts. 4) Enforce strong password policies and consider deploying alternative 2FA solutions that do not exhibit this vulnerability. 5) Monitor logs for unusual authentication attempts or repeated PIN validation failures indicative of brute-force activity. 6) Engage with the plugin vendor or Atlassian support channels to obtain patches or updates as soon as they become available. 7) Educate users about the risk and encourage vigilance for suspicious account activity. 8) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block exploitation attempts targeting this endpoint. These targeted mitigations go beyond generic advice by focusing on controlling access to the vulnerable endpoint and enhancing detection capabilities until an official patch is released.

Description

The Syracom Secure Login (2FA) plugin for Jira, Confluence, and Bitbucket through 3.1.4.5 allows remote attackers to easily brute-force the 2FA PIN via the plugins/servlet/twofactor/public/pinvalidation endpoint. The last 30 and the next 30 tokens are valid.

Impact

The impact of CVE-2024-48942 is significant for organizations relying on Atlassian Jira, Confluence, and Bitbucket with the Syracom Secure Login 2FA plugin. Successful exploitation allows attackers to bypass two-factor authentication, effectively nullifying a critical security control designed to prevent unauthorized access. This can lead to unauthorized access to sensitive project management data, source code repositories, and internal documentation, potentially resulting in intellectual property theft, data breaches, and disruption of business operations. The integrity of user accounts and data can be compromised, enabling attackers to impersonate legitimate users and perform unauthorized actions. Since the vulnerability requires no authentication and no user interaction, it can be exploited remotely and at scale, increasing the risk of widespread compromise. Organizations in sectors with high reliance on Atlassian tools, such as software development, finance, government, and critical infrastructure, face elevated risks. The absence of known exploits in the wild provides a window for mitigation, but the critical severity demands immediate attention to prevent potential attacks.

CWE-799Improper Control of Interaction Frequency (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

syracom-bee.atlassian.net/wiki/spaces/SL/pages/3236560898/2024-09-16+-+Secure+Login+security+advisory+-+Insecure+default+configuration (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 00:22 UTC

WeaknessesCWE-799

Technical details

References

Community reviews

Related threats