# CVE-2013-6807: Weak cryptography in n/a

> Man-in-the-middle attackers can bypass certificate validation and intercept sensitive data due to default anonymous cipher support in the client.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qh2r-5cxf-8cc6

## What is CVE-2013-6807?

CVE-2013-6807 is a medium-severity vulnerability in n/a, published on 19 May 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The client in OpenText Exceed OnDemand (EoD) 8 supports anonymous ciphers by default, which allows man-in-the-middle attackers to bypass server certificate validation, redirect a connection, and obtain sensitive information via crafted responses.

Weakness: CWE-310

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

It affects 1 product.


Products: Opentext Exceed Ondemand.

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

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

## Is CVE-2013-6807 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6806](https://insights.sbomify.com/CVE-2013-6806/): Security feature bypass 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-6807 and fix it if it is affected.

What it is: CVE-2013-6807 is a medium-severity vulnerability in n/a, published on 19 May 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-6807 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-6807/ (Markdown: https://insights.sbomify.com/CVE-2013-6807/index.md)
```

## Sources

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

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