# CVE-2006-6477: Security feature bypass in n/a

> Local attackers can hijack HTTP daemon traffic in Mandiant First Response to perform man-in-the-middle attacks, requiring HTTP-only configuration.

- **Severity:** Low 2.4 (`AV:L/AC:H/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fvjv-64gm-6hrw

## What is CVE-2006-6477?

CVE-2006-6477 is a low-severity vulnerability in n/a, published on 20 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FRAgent.exe in Mandiant First Response (MFR) before 1.1.1, when run in daemon mode and configured to use only HTTP, allows local users to modify requests and responses between a client and an agent by hijacking an HTTP FRAgent daemon and conducting a man-in-the-middle (MITM) attack.

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

It affects 1 product.


Products: Mandiant First Response.

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

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

## Is CVE-2006-6477 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6475](https://insights.sbomify.com/CVE-2006-6475/): Denial of service in n/a (high 7.1)
- [CVE-2006-6476](https://insights.sbomify.com/CVE-2006-6476/): Race condition in n/a (low 2.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6477 is a low-severity vulnerability in n/a, published on 20 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6477 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-2006-6477/ (Markdown: https://insights.sbomify.com/CVE-2006-6477/index.md)
```

## Sources

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

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