Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| aehrc | pathling | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aehrc | Pathling |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.543% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aehrc
Aehrc pathling |
|
| Vendors & Products |
Aehrc
Aehrc pathling |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Pathling is a set of tools that make it easier to use FHIR and clinical terminology within health data analytics. Prior to version 2.0.0 of Pathling Server, Pathling's bulk-submit operation allows an allowed submitter to supply an explicit `oauthMetadataUrl` parameter that is not validated against `pathling.bulkSubmit.allowableSources`. When present, the bulk-submit OAuth flow trusts metadata and the returned `token_endpoint` from the caller-chosen location, then builds outbound OAuth client authentication directly from the submitter's stored credentials. This is fixed in Pathling Server 2.0.0. | |
| Title | Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration | |
| Weaknesses | CWE-522 CWE-918 |
|
| References |
| |
| Metrics |
cvssV4_0
|