CVE-2020-6267
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 · uneditedSome sensitive cookies in SAP Disclosure Management, version 10.1, are missing HttpOnly flag, leading to sensitive cookie without Http Only flag.
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 confidenceIn SAP Disclosure Management version 10.1, certain sensitive cookies (typically session cookies) are served without the HttpOnly flag. This flag prevents client-side JavaScript from accessing the cookie content. Without it, if a cross-site scripting (XSS) vulnerability exists elsewhere in the application, attackers could potentially steal session cookies to impersonate legitimate users.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm SAP Disclosure Management versionLocate the installed version of SAP Disclosure Management in your system (check SAP LM structure, installed programs, or application about page)Affected if Version is 10.1 exactly
-
Identify application session cookiesAccess the SAP Disclosure Management web interface and authenticate. Use browser developer tools (Application > Cookies) or run 'curl -I <dm_url>' to capture HTTP response headersAffected if Application uses session cookies such as JSESSIONID or similar session identifiers
-
Inspect Set-Cookie headers for HttpOnly flagExamine the Set-Cookie HTTP response headers from the application server. Look for the HttpOnly attribute in each cookie specificationAffected if Session cookies are present WITHOUT the HttpOnly attribute in the Set-Cookie header (e.g., 'Set-Cookie: JSESSIONID=...; path=/' without HttpOnly)
-
Verify cookie access via client-side scriptOpen browser console on the SAP Disclosure Management page and run 'document.cookie' to confirm JavaScript can read session cookie valuesAffected if JavaScript can access session cookie contents (cookie appears in document.cookie output)
You are affected if running SAP Disclosure Management 10.1 and session cookies lack the HttpOnly flag, allowing potential XSS-based 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 the application server or application code to set the HttpOnly attribute on all sensitive cookies. In SAP Disclosure Management, this typically involves adjusting the session cookie configuration or web.xml settings to ensure the flag is applied during cookie creation.
- 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-2020-6267 — 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-6267 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