# CVE-2024-48942: Security feature bypass in n/a

> Attackers can bypass two-factor authentication by brute-forcing PINs due to a wide validity window, leading to account takeover.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2024
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-hqhf-c9cf-w4qm

## What is CVE-2024-48942?

CVE-2024-48942 is a critical vulnerability in n/a, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-799 (Improper Control of Interaction Frequency)

## Which versions are affected by CVE-2024-48942?

It affects 1 product.


Products: Syracom Secure Login.

## How do I fix CVE-2024-48942?

No fix has been published for CVE-2024-48942 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48942 being exploited?

There is no known exploitation of CVE-2024-48942 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-48941](https://insights.sbomify.com/CVE-2024-48941/): Auth bypass in n/a (critical 9.1)
- [CVE-2023-22958](https://insights.sbomify.com/CVE-2023-22958/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48942 and fix it if it is affected.

What it is: CVE-2024-48942 is a critical vulnerability in n/a, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48942 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48942/ (Markdown: https://insights.sbomify.com/CVE-2024-48942/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48942
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48942
- OSV: https://osv.dev/vulnerability/CVE-2024-48942

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48942/
Summaries are generated and may contain mistakes; the official description above is the record.