GHSA-gj7p-595x-qwf5
Fix: datasharingframework/dsf@7d25feaGHSA-gj7p-595x-qwf5 is a CWE-613 vulnerability in dev.dsf:dsf-common-jetty. O3 Security confirms whether GHSA-gj7p-595x-qwf5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Data Sharing Framework is Missing Session Timeout for OIDC Sessions
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
dev.dsf:dsf-common-jetty☕dev.dsf:dsf-fhir-server☕dev.dsf:dsf-bpe-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Affected Components
DSF FHIR Server with enabled OIDC authentication. DSF BPE Server with enabled OIDC authentication.
Summary
OIDC-authenticated sessions had no configured maximum inactivity timeout. Sessions persisted indefinitely after login, even after the OIDC access token expired.
Impact
If a user logs in via OIDC and leaves their browser without explicitly logging out, the session remains valid indefinitely. Another person using the same browser can access the DSF UI with the previous user's permissions. This is a realistic threat in hospital environments with shared workstations.
Only affects OIDC browser sessions, not relevant for mTLS machine-to-machine communication.
Fix (commits f4ecb00, 7d25fea)
- Added configurable session timeout via
dev.dsf.server.auth.oidc.session.timeout(default:PT30M). - Enabled
logoutWhenIdTokenIsExpired(true)in OpenID configuration to tie session lifetime to token lifetime. - Websocket sessions are now closed with
VIOLATED_POLICYwhen credentials expire, prevents stale websocket connections from continuing to receive events after session timeout.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | dev.dsf:dsf-common-jetty | all versions | No fix |
| ☕Maven | dev.dsf:dsf-fhir-server | all versions | No fix |
| ☕Maven | dev.dsf:dsf-bpe-server | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dev.dsf:dsf-common-jetty. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of dev.dsf:dsf-common-jetty has shipped for GHSA-gj7p-595x-qwf5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gj7p-595x-qwf5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-gj7p-595x-qwf5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gj7p-595x-qwf5 in your dependencies?
O3 detects GHSA-gj7p-595x-qwf5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.