CVE-2020-14247
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 · uneditedHCL OneTest Performance V9.5, V10.0, V10.1 contains an inadequate session timeout, which could allow an attacker time to guess and use a valid session ID.
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 confidenceHCL OneTest Performance versions 9.5, 10.0, and 10.1 have inadequate session timeout configuration, meaning user sessions remain active for an excessively long period. This extended session lifetime provides attackers a larger time window to guess, intercept, or reuse valid session IDs, potentially leading to session hijacking or unauthorized access.
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= 9.5.0= 10.0.0= 10.1.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 installed HCL OneTest Performance versionCheck the product version through the installed software information, product UI about section, or installation directory version file. Common locations include the installation root folder or Windows Add/Remove Programs.Affected if The installed version is exactly 9.5.0, 10.0.0, or 10.1.0
-
Locate session timeout configurationFind the session timeout settings in the application server hosting HCL OneTest Performance (typically IBM WebSphere) or the product's own configuration files. Look for session timeout parameters in web.xml, ibm-web-ext.xmi, or the WebSphere administrative console session configuration.Affected if The configuration files or application server settings are accessible and show session timeout values
-
Verify session timeout durationInspect the session timeout value - it is typically defined in minutes. Check if the timeout is set to a duration significantly longer than the recommended 15-30 minute range.Affected if The session timeout is configured to 30 minutes or more, or set to an unlimited duration (such as -1 or no timeout)
-
Confirm active session behaviorLog in to the application and observe whether the session remains valid after an extended period of inactivity (30+ minutes without interaction).Affected if The session remains active after 30 minutes of inactivity, indicating the timeout is set too high
You are affected if you are running HCL OneTest Performance version 9.5.0, 10.0.0, or 10.1.0 AND your session timeout is configured to an excessively long duration (30+ minutes or unlimited), which extends the attack window for session hijacking.
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 dataConfigure appropriate session timeout values (typically 15-30 minutes of inactivity) and ensure sessions are invalidated properly after logout or idle timeout. Consider implementing additional session security measures such as session rotation on authentication and secure session cookie attributes.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14247 — 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-2020-14247 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