DSF: Inverted Time Comparison in OIDC JWKS and Token Cache
datasharingframework dsf · dev.dsf dsf-bpe-process-api-v2 · dev.dsf dsf-bpe-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| dev.dsf:dsf-bpe-process-api-v2 Maven |
| No fix yet |
| dev.dsf:dsf-bpe-server Maven |
| No fix yet |
Original description
The Data Sharing Framework (DSF) implements a distributed process engine based on the BPMN 2.0 and FHIR R4 standards. Prior to 2.1.0, The OIDC JWKS and Metadata Document caches used an inverted time comparison (isBefore instead of isAfter), causing the cache to never return cached values. Every incoming request triggered a fresh HTTP fetch of the OIDC Metadata Document and JWKS keys from the OIDC provider. The OIDC token cache for the FHIR client connections used an inverted time comparison (isBefore instead of isAfter), causing the cache to never invalidate. Every incoming request returned the same OIDC token even if expired. This vulnerability is fixed in 2.1.0.