# CVE-2006-7167: Auth bypass in n/a

> Remote attackers can bypass authentication in ProRat Server to gain unauthorized access and control.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x5c6-jp5f-h749

## What is CVE-2006-7167?

CVE-2006-7167 is a high-severity authentication bypass vulnerability in n/a, published on 20 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in ProRat Server 1.9 Fix2 allows remote attackers to bypass the authentication mechanism for remote login via unspecified vectors.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2006-7167?

It affects 1 product.


Products: Prorat Server.

## How do I fix CVE-2006-7167?

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

## Is CVE-2006-7167 being exploited?

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

Public exploit code:

- ProRat Server 1.9 (Fix-2) - Buffer Overflow / Crash (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7167 and fix it if it is affected.

What it is: CVE-2006-7167 is a high-severity authentication bypass vulnerability in n/a, published on 20 Mar 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-2006-7167 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-2006-7167/ (Markdown: https://insights.sbomify.com/CVE-2006-7167/index.md)
```

## Sources

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

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