# CVE-2012-6066: Auth bypass in n/a

> Remote attackers can bypass authentication in freeSSHd by sending a crafted session, gaining unauthorized access to the SSH server.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 4 Dec 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jmwc-3jq9-gh6r

## What is CVE-2012-6066?

CVE-2012-6066 is a critical authentication bypass vulnerability in n/a, published on 4 Dec 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

freeSSHd.exe in freeSSHd through 1.2.6 allows remote attackers to bypass authentication via a crafted session, as demonstrated by an OpenSSH client with modified versions of ssh.c and sshconnect2.c.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-6066?

It affects 1 product.


Products: Freesshd Freesshd.

## How do I fix CVE-2012-6066?

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

## Is CVE-2012-6066 being exploited?

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

Public exploit code:

- Freesshd Authentication Bypass (metasploit)
- freeFTPd 1.2.6 - Remote Authentication Bypass (exploitdb)
- freeSSHd 2.1.3 - Remote Authentication Bypass (exploitdb)
- freeSSHd 1.2.6 - Authentication Bypass (Metasploit) (exploitdb)
- FreeSSHD Remote Authentication Bypass Vulnerability (freeSSHd 2.1.3) (github_poc): https://github.com/bongbongco/CVE-2012-6066

## Other vulnerabilities in n/a

- [CVE-2018-9853](https://insights.sbomify.com/CVE-2018-9853/): Privilege escalation in n/a (critical 9.8)
- [CVE-2008-6899](https://insights.sbomify.com/CVE-2008-6899/): Memory corruption in n/a (critical 9.0)
- [CVE-2008-4762](https://insights.sbomify.com/CVE-2008-4762/): Memory corruption in n/a (critical 9.0)
- [CVE-2008-2573](https://insights.sbomify.com/CVE-2008-2573/): Memory corruption in n/a (high 8.5)
- [CVE-2017-1000475](https://insights.sbomify.com/CVE-2017-1000475/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6066 and fix it if it is affected.

What it is: CVE-2012-6066 is a critical authentication bypass vulnerability in n/a, published on 4 Dec 2012. 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-2012-6066 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-2012-6066/ (Markdown: https://insights.sbomify.com/CVE-2012-6066/index.md)
```

## Sources

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

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