# CVE-2013-6806: Security feature bypass in n/a

> Man-in-the-middle attackers can bypass bidirectional authentication and steal plaintext credentials by forcing a downgrade to simple authentication in OpenText Exceed OnDemand.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 19 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j7p4-2vqr-pgcw

## What is CVE-2013-6806?

CVE-2013-6806 is a medium-severity vulnerability in n/a, published on 19 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenText Exceed OnDemand (EoD) 8 allows man-in-the-middle attackers to disable bidirectional authentication and obtain sensitive information via a crafted string in a response, which triggers a downgrade to simple authentication that sends credentials in plaintext.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-6806?

It affects 1 product.


Products: Opentext Exceed Ondemand.

## How do I fix CVE-2013-6806?

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

## Is CVE-2013-6806 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6807](https://insights.sbomify.com/CVE-2013-6807/): Weak cryptography in n/a (medium 6.8)
- [CVE-2013-6994](https://insights.sbomify.com/CVE-2013-6994/): Information disclosure in n/a (medium 6.4)
- [CVE-2013-6805](https://insights.sbomify.com/CVE-2013-6805/): Weak cryptography in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6806 and fix it if it is affected.

What it is: CVE-2013-6806 is a medium-severity vulnerability in n/a, published on 19 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6806 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-2013-6806/ (Markdown: https://insights.sbomify.com/CVE-2013-6806/index.md)
```

## Sources

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

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