CVE-2013-6806
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenText 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenText Exceed OnDemand 8 is vulnerable to a man-in-the-middle attack where attackers send a crafted string in a response to disable bidirectional authentication. This downgrades authentication to a simple mode that transmits user credentials in plaintext, allowing the attacker to intercept sensitive authentication data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Exceed OnDemand versionCheck the installed version of OpenText Exceed OnDemand by reviewing the program files, running 'xondmd -v' or checking the Windows Add/Remove Programs list for version 8.0Affected if Version is exactly 8.0
-
Locate Exceed OnDemand configuration fileFind the xodm.cfg or xodm.ini configuration file in the Exceed OnDemand installation directory (commonly in C:\Program Files\OpenText\Exceed OnDemand or similar)Affected if Configuration file exists and is accessible
-
Check authentication mode settingInspect the configuration file for the 'SimpleAuth' or 'SimpleAuthEnabled' setting and verify whether it is set to '1', 'yes', 'on', or 'true'Affected if Simple authentication is explicitly enabled in the configuration
-
Inspect authentication protocol settingsLook for 'BidirectionalAuth', 'SecureAuth', or similar authentication-related settings in the configuration file to confirm whether bidirectional/secure authentication is disabled or not configuredAffected if Bidirectional authentication is disabled, not set, or set to a non-secure value
You are affected if OpenText Exceed OnDemand version 8.0 is installed AND simple authentication mode is enabled in the configuration file, allowing plaintext credential transmission vulnerable to MITM interception.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable simple authentication in Exceed OnDemand configuration to prevent authentication downgrade. Implement network-level controls (such as VPN or network segmentation) to block MITM attacks. Apply any available vendor patches for Exceed OnDemand.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6806 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data