CVE-2020-6291
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 · uneditedSAP Disclosure Management, version 10.1, session mechanism does not have expiration data set therefore allows unlimited access after authenticating once, leading to Insufficient Session Expiration
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 confidenceSAP Disclosure Management version 10.1 contains a session management flaw where the session mechanism lacks expiration data, allowing authenticated sessions to remain valid indefinitely after initial login.
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= 10.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 SAP Disclosure Management installation and versionLocate the SAP Disclosure Management installation directory or check installed programs list. Look for version information in the application metadata, About dialog, or installation logs. Confirm the exact version number is 10.1.Affected if The installed version of SAP Disclosure Management is exactly 10.1
-
Examine session configuration filesNavigate to the SAP Disclosure Management configuration directory. Look for session-related configuration files such as web.xml, session-config.xml, or similar files in the conf or config folders. Inspect the session-timeout parameter if present.Affected if Session timeout is not configured or set to a value that allows indefinite sessions (null, 0, or very high value)
-
Check application session management settingsAccess the SAP Disclosure Management administrative console or configuration interface. Locate session management settings. Verify whether session expiration parameters are defined and properly set.Affected if No session expiration timeout is defined or sessions are configured to persist without time limits
-
Inspect session cookie behaviorLog into the application using a test account. Use browser developer tools or a network proxy to observe the session cookie (often JSESSIONID or similar). Check if the cookie lacks an expiration attribute (indicating session cookie) or has an overly long Max-Age.Affected if Session cookies do not have a reasonable expiration time set or remain valid after browser closure
A user is affected if SAP Disclosure Management version 10.1 is installed and session configuration allows authenticated sessions to persist indefinitely without timeout.
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 dataImplement proper session timeout and expiration controls in the session management layer to enforce reasonable session lifetimes and automatic invalidation after periods of inactivity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6291 — 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-6291 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