dbcve.org
Secure LoginApplication · Syracom

CVE-2024-48942

MEDIUM · 5.9 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to after 3.1.4.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Syracom Secure Login 2FA plugin for Jira, Confluence, and Bitbucket versions through 3.1.4.5 contains a weak token validation flaw. The /plugins/servlet/twofactor/public/pinvalidation endpoint accepts not just the current valid token but also the previous 30 and next 30 tokens, effectively providing a 60-token window that all authenticate successfully. This makes brute-force attacks trivial since an attacker has a 1-in-1000 chance (rather than 1-in-1,000,000) of guessing a valid 6-digit PIN.

MitigationUpgrade to the patched version of the Syracom Secure Login plugin (contact vendor for fixed release). As an interim control, implement aggressive rate limiting or IP-based blocking on the pinvalidation endpoint, and monitor for authentication anomalies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Secure LoginApplication
Affected:<= 3.1.4.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Syracom Secure Login plugin is installed
    Access Atlassian administration console (Manage apps or Apps > Find new apps) and search for 'Syracom Secure Login' or 'Secure Login 2FA' in the installed plugins list
    Affected if The plugin appears in the installed applications list
  2. Check installed plugin version
    In the Atlassian admin console, click on the Syracom Secure Login plugin details to view the version number; compare against 3.1.4.5 (any version equal to or lower than 3.1.4.5 is affected)
    Affected if Version displayed is 3.1.4.5 or earlier
  3. Confirm the vulnerable endpoint exists and responds
    Send a POST request to /plugins/servlet/twofactor/public/pinvalidation with a test PIN payload (e.g., {"pin":"000000"}); check if the endpoint accepts the request and returns an authentication response
    Affected if The endpoint responds to PIN validation requests
  4. Verify 2FA is enabled for users
    Check the plugin configuration in Atlassian administration under Secure Login settings, or review user security settings to confirm two-factor authentication is active for the Jira/Confluence/Bitbucket instance
    Affected if 2FA/Secure Login is enabled and enforced for users in the environment
  5. Audit authentication logs for brute-force patterns
    Review Atlassian access logs or security audit logs for repeated requests to /plugins/servlet/twofactor/public/pinvalidation with varying PIN values from the same IP or session; look for success rate anomalies
    Affected if Logs show high-volume PIN attempts or multiple successful authentications in short succession from the same source

Your environment is affected if the Syracom Secure Login plugin version is 3.1.4.5 or earlier AND the 2FA feature is enabled, making the /plugins/servlet/twofactor/public/pinvalidation endpoint vulnerable to trivial brute-force attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3.1.4.5
Interim mitigation

Upgrade to the patched version of the Syracom Secure Login plugin (contact vendor for fixed release). As an interim control, implement aggressive rate limiting or IP-based blocking on the pinvalidation endpoint, and monitor for authentication anomalies.

Fix this in Secure Login Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48942 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data