CVE-2024-35189: Sensitive Data Disclosure Vulnerability in Connection Configuration Endpoints
The Fides webserver has a number of endpoints that retrieve ConnectionConfiguration records and their associated secrets which can contain sensitive data (e.g. passwords, private keys, etc.). These secrets are stored encrypted at rest (in the application database), and the associated endpoints are not meant to expose that sensitive data in plaintext to API clients, as it could be compromising.
Published Jun 2, 2024
Affected packages
ethyca-fides
- Ecosystem
- PyPI
- Affected
- < 2.37.0
- Fixed in
- 2.37.0
- Check
pip show ethyca-fides
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
The Fides webserver has a number of endpoints that retrieve ConnectionConfiguration records and their associated secrets which _can_ contain sensitive data (e.g. passwords, private keys, etc.). These secrets are stored encrypted at rest (in the application database), and the associated endpoints are not meant to expose that sensitive data in plaintext to API clients, as it could be compromising.
Fides's developers have available to them a Pydantic field-attribute (sensitive) that they can annotate as True to indicate that a given secret field should not be exposed via the API. The application has an internal function that uses sensitive annotations to mask the sensitive fields with a "**********" placeholder value.
This vulnerability is due to a bug in that function, which prevented sensitive API model fields that were _nested_ below the root-level of a secrets object from being masked appropriately. Only the BigQuery connection configuration secrets meets these criteria: the secrets schema has a nested sensitive keyfile_creds.private_key property that is exposed in plaintext via the APIs.
Connection types other than BigQuery with sensitive fields at the root-level that are not nested are properly masked with the placeholder and are not affected by this vulnerability.
Impact
The Google Cloud secrets used for a Fides BigQuery integration may be retrieved in plaintext by any authenticated Admin UI user, except those with the Approver role. Any API users authorized to access the following endpoints may also retrieve the key in plaintext.
Endpoints impacted:
GET /api/v1/connectionsPATCH /api/v1/connectionsGET /api/v1/connection/{connection_key}PATCH /api/v1/system/{system_key}/connectionGET /api/v1/system/{system_key}GET /api/v1/system/{system_key}/connection
Connection config secret schemas impacted:
BigQuerySchema
Patches
The vulnerability has been patched in Fides version 2.37.0. Users are advised to upgrade to this version or later to secure their systems against this threat.
Users are also advised to rotate any Google Cloud secrets used for BigQuery integrations in their Fides deployments: https://cloud.google.com/iam/docs/key-rotation
Workarounds
There are no workarounds.
Proof of concept
Multiple endpoints are impacted, but this PoC will use GET /api/v1/system/{system_key} as an example.
- Using the Admin UI, navigate to
/add-systems. Add and save a new systembq_poc. - In the integrations tab of the new system, configure and save a BigQuery integration with secrets.
- Log in as a different user with any role except Approver and navigate to the
/systemspage. - Open the network section of your browser's developer tools.
- Click on the
bq_pocsystem's meatball menu and then click edit. - In the network section of browser dev tools you will observe a HTTP GET http://localhost:8080/api/v1/system/bq_poc/ request. In the body of the JSON response the integration secrets values entered in Step 2 are exposed in plaintext i.e.
{
"secrets": {
"keyfile_creds": {
"type": "value",
"project_id": "value",
"private_key_id": "value",
"private_key": "value",
"client_email": "value",
"client_id": "value",
"auth_uri": "value",
"token_uri": "value",
"auth_provider_x509_cert_url": "value",
"client_x509_cert_url": "value"
}
}
}Credited to adamsachs.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-44541
ethyca-fides has a DOM-based XSS vulnerability in fides.js via fides_description override
high7.0May 14, 2026CVE-2026-42303
Ethyca Fides has a Privacy Request Identity Verification Bypass Vulnerability via Duplicate Detection
medium6.1May 5, 2026CVE-2025-57766
Fides' Admin UI User Password Change Does Not Invalidate Current Session
low4.8Sep 8, 2025CVE-2025-57815
Fides has a Lack of Brute-Force Protections on Authentication Endpoints
low6.5Sep 8, 2025CVE-2025-57816
Fides Webserver API Rate Limiting Vulnerability in Proxied Environments
medium7.5Sep 8, 2025CVE-2025-57817
Fides Webserver API is Vulnerable to OAuth Client Privilege Escalation
high7.2Sep 8, 2025
