# CVE-2024-9999: Multi-Factor Authentication Bypass in Progress WS_FTP Server

> Attackers can bypass multi-factor authentication in WS_FTP Server to log in with only username and password, gaining unauthorized access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-fgq7-v63g-3f6x

## What is CVE-2024-9999?

CVE-2024-9999 is a medium-severity authentication bypass vulnerability in Progress Software Corporation WS_FTP Server, published on 12 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In WS_FTP Server versions before 8.8.9 (2022.0.9), an Incorrect Implementation of Authentication Algorithm in the Web Transfer Module allows users to skip the second-factor verification and log in with username and password only.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

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


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

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

## Is CVE-2024-9999 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9999 is a medium-severity authentication bypass vulnerability in Progress Software Corporation WS_FTP Server, published on 12 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-9999 in the wild and no public exploit code.

Affected product: Progress Software Corporation WS_FTP Server. 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-9999/ (Markdown: https://insights.sbomify.com/CVE-2024-9999/index.md)
```

## Sources

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

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