CVE-2013-6805
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 uses weak encryption for passwords, which makes it easier for (1) remote attackers to discover credentials by sniffing the network or (2) local users to discover credentials by reading a .eod8 file.
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 stores user credentials using weak encryption in .eod8 configuration files and transmits them over the network without adequate protection, allowing remote attackers to recover plaintext passwords via network sniffing and local users to read plaintext passwords from configuration files.
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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Identify Exceed OnDemand installationCheck for Exceed OnDemand 8.0 installation by looking for the application in Program Files or checking registry keys related to OpenText/Exceed OnDemandAffected if Version 8.0 of Exceed OnDemand is installed
-
Locate .eod8 configuration filesSearch the filesystem for .eod8 configuration files, typically found in user profile directories or application data folders (e.g., %APPDATA%\OpenText\Exceed OnDemand or similar paths)Affected if The system contains .eod8 configuration files storing user credentials
-
Inspect credential storage methodOpen a .eod8 configuration file in a text editor or hex viewer and examine how passwords are stored - look for encoded/encrypted strings that differ from plaintextAffected if Credentials in .eod8 files use weak or reversible encryption rather than strong encryption like AES-256
-
Verify network credential transmissionCapture network traffic during authentication using a packet sniffer (such as Wireshark) and examine whether credentials are sent in plaintext or with weak encoding over the networkAffected if User credentials are transmitted over the network without TLS/SSL encryption or using weak encoding
A user is affected if they run Exceed OnDemand 8.0 with credentials stored in .eod8 files using weak encryption or transmitted over the network without adequate protection.
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 dataUpgrade to a version with strong password encryption (e.g., AES-256) and ensure all network communication uses TLS/SSL. Alternatively, implement a secure credential storage mechanism and enforce encrypted transport for all authentication traffic.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6805 — 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-6805 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