CVE-2013-6994
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 transmits the session ID in cleartext, which allows remote attackers to perform session fixation attacks by sniffing the network.
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 (EoD) version 8 transmits session IDs in cleartext over the network, enabling remote attackers who can sniff network traffic to capture valid session IDs and perform session fixation attacks.
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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Confirm Exceed OnDemand versionCheck the installed version of OpenText Exceed OnDemand. This is typically available in the application properties, about dialog, or installation directory version file. Compare against the affected version 8.0.Affected if The installed version is exactly 8.0 (or falls within the = 8.0 range specified)
-
Inspect network traffic for session ID transmissionUse a network packet capture tool (such as Wireshark or tcpdump) to capture traffic between the Exceed OnDemand client and server during session establishment and authentication. Examine the captured packets to determine if session identifiers are transmitted in cleartext (unencrypted).Affected if Session IDs are visible in plaintext within captured network packets
-
Verify if TLS/SSL encryption is configuredCheck the Exceed OnDemand server and client configuration settings for SSL/TLS encryption options. Look for encryption-related settings in the server configuration files or administrative console.Affected if TLS/SSL encryption is not enabled or is disabled in the configuration
-
Check session ID handling after authenticationExamine the session management configuration or logs to determine whether session IDs are regenerated (new session identifier issued) after successful user authentication, rather than retaining the pre-authentication session ID.Affected if Session IDs are not regenerated after authentication - the same ID persists throughout the session
A user is affected if Exceed OnDemand version 8.0 is installed AND sessions are transmitted without TLS/SSL encryption AND session IDs are not regenerated after authentication, allowing session fixation via cleartext network sniffing.
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 dataEnable TLS/SSL encryption for all Exceed OnDemand sessions and implement session ID regeneration after successful authentication to prevent session fixation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6994 — 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-6994 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