# CVE-2002-2417: Auth bypass in n/a

> Remote attackers can bypass authentication logging and potentially gain privileges in acFTP by providing invalid passwords.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-62gr-x8g8-959r

## What is CVE-2002-2417?

CVE-2002-2417 is a critical authentication bypass vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

acFTP 1.4 does not properly handle when an invalid password is provided by the user during authentication, which allows remote attackers to hide or misrepresent certain activity from log files and possibly gain privileges.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2002-2417?

It affects 1 product.


Products: Acftp Acftp.

## How do I fix CVE-2002-2417?

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

## Is CVE-2002-2417 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-2417 exists.

Public exploit code:

- acFTP 1.4 - Invalid Password Weak Authentication (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-2242](https://insights.sbomify.com/CVE-2006-2242/): Denial of service in n/a (medium 5.0)
- [CVE-2006-6775](https://insights.sbomify.com/CVE-2006-6775/): Denial of service in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2417 and fix it if it is affected.

What it is: CVE-2002-2417 is a critical authentication bypass vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-2417 exists.

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-2002-2417/ (Markdown: https://insights.sbomify.com/CVE-2002-2417/index.md)
```

## Sources

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

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