CVE-2023-25562
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 · uneditedDataHub is an open-source metadata platform. In versions of DataHub prior to 0.8.45 Session cookies are only cleared on new sign-in events and not on logout events. Any authentication checks using the `AuthUtils.hasValidSessionCookie()` method could be bypassed by using a cookie from a logged out session, as a result any logged out session cookie may be accepted as valid and therefore lead to an authentication bypass to the system. Users are advised to upgrade. There are no known workarounds for this issue. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-083.
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 DataHub versions prior to 0.8.45, session cookies are only invalidated when a new sign-in event occurs but are not cleared during logout events. The AuthUtils.hasValidSessionCookie() method accepts any previously issued session cookie as valid, even after the user has logged out, enabling an attacker with a stale cookie to bypass authentication and access the system.
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< 0.8.45CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 DataHub versionRun the following command to check the installed DataHub version: `datahub --version` or check the version in your package manager, build configuration, or Docker image tag. Alternatively, check the version in the DataHub UI under 'About' or 'Settings' if available.Affected if The installed version is lower than 0.8.45
-
Locate AuthUtils source codeSearch the DataHub codebase for the AuthUtils class file, typically found in the authentication module. Look for a file named AuthUtils.java or similar that contains the method `hasValidSessionCookie()`.Affected if The code shows that hasValidSessionCookie() validates cookies without checking a logout/invalidation timestamp
-
Inspect session cookie handling on logoutReview the logout endpoint or function in the codebase. Look for how session cookies are handled when the `/logout` endpoint is called. Check if session cookies are explicitly cleared or invalidated versus being left intact.Affected if The logout process does not clear or invalidate the session cookie, leaving it valid for reuse
-
Review session cookie persistence after logoutIf you have access to a test environment, perform a login, capture the session cookie value, call the logout endpoint, then attempt to use the original cookie value in a subsequent authenticated request.Affected if The original session cookie remains valid after logout and allows authenticated access
You are affected if DataHub version is below 0.8.45 and the logout implementation does not invalidate session cookies.
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.
dbcve · scoped0.8.45
Upgrade DataHub to version 0.8.45 or later where session cookies are properly invalidated on logout events.
0.8.45
- 1. Back up your current DataHub installation and configuration
- 2. Upgrade DataHub to version 0.8.45 or later
- 3. Verify the upgrade was successful by checking the DataHub version
- 4. Test that session cookies are properly cleared upon logout
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25562 — 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-2023-25562 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