CVE-2024-35189: Ethyca fides Sensitive Data Disclosure Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-rcvg-jj3g-rj7c
CVSS 6.5
CWE-200
Published
Advisory Summary

CVE-2024-35189 is a MODERATE (CVSS 6.5) sensitive data disclosure vulnerability vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Ethyca fides libraries in the PyPI ecosystem. The issue involves sensitive data disclosure vulnerability in connection configuration endpoints. Remediation is available by upgrading affected packages to version 2.37.0.

CVE-2024-35189 at a Glance

CVE Identifier CVE-2024-35189
GHSA Identifier GHSA-rcvg-jj3g-rj7c
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Ethyca fides
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-35189

To remediate this vulnerability, upgrade all affected Ethyca fides dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

ethyca-fides fixed: 2.37.0
pip install ethyca-fides>=2.37.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show ethyca-fides

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2024-35189, inspect your installed packages using pip:

pip show ethyca-fides

Analyze the terminal output to locate any version of Ethyca fides in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.37.0), your application is affected.

Note: The pip show ethyca-fides command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Ethyca fides, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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/connections` - `PATCH /api/v1/connections` - `GET /api/v1/connection/{connection_key}` - `PATCH /api/v1/system/{system_key}/connection` - `GET /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. 1. Using the Admin UI, navigate to `/add-systems`. Add and save a new system `bq_poc`. 2. In the integrations tab of the new system, configure and save a BigQuery integration with secrets. 3. Log in as a different user with any role except Approver and navigate to the `/systems` page. 4. Open the network section of your browser's developer tools. 5. Click on the `bq_poc` system's meatball menu and then click edit. 6. 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. ```json { "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" } } } ```

CVE-2024-35189 Affected Ethyca fides Versions

1 component(s)
Fixed Versions:
2.37.0
Product / Package Ecosystem Affected Versions Fixed Version
ethyca-fides
PyPI
< 2.37.0
2.37.0

References

Frequently Asked Questions

What is CVE-2024-35189?
CVE-2024-35189 is a security vulnerability in Ethyca fides involving Sensitive Data Disclosure Vulnerability in Connection Configuration Endpoints under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Ethyca fides versions are affected?
Affected versions include releases prior to 2.37.0 across affected packages: ethyca-fides.
What version fixes CVE-2024-35189?
Upgrading to 2.37.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ethyca-fides affected?
Yes, ethyca-fides is affected in releases prior to 2.37.0. Upgrade your dependency to 2.37.0 or later.
What is the CVSS score of CVE-2024-35189?
CVE-2024-35189 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2024-35189?
CVE-2024-35189 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check PyPI dependencies for CVE-2024-35189?
Run the dependency tree command: 'pip show ethyca-fides'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rcvg-jj3g-rj7c",
  "modified" : "2024-06-02T22:28:03Z",
  "published" : "2024-06-02T22:28:03Z",
  "aliases" : [ "CVE-2024-35189" ],
  "summary" : "Sensitive Data Disclosure Vulnerability in Connection Configuration Endpoints",
  "details" : "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. \n\nFides'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.\n\nThis 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.\n\nConnection 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.\n\n\n### Impact\n\nThe 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.\n\nEndpoints impacted:\n- `GET /api/v1/connections`\n- `PATCH /api/v1/connections`\n- `GET /api/v1/connection/{connection_key}`\n- `PATCH /api/v1/system/{system_key}/connection`\n- `GET /api/v1/system/{system_key}`\n- `GET /api/v1/system/{system_key}/connection`\n\nConnection config secret schemas impacted:\n- `BigQuerySchema`\n\n### Patches\nThe 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.\n\nUsers 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\n\n### Workarounds\nThere are no workarounds.\n\n### Proof of concept\n\nMultiple endpoints are impacted, but this PoC will use `GET /api/v1/system/{system_key}` as an example.\n\n1. Using the Admin UI, navigate to `/add-systems`. Add and save a new system `bq_poc`.\n2. In the integrations tab of the new system, configure and save a BigQuery integration with secrets.\n3. Log in as a different user with any role except Approver and navigate to the `/systems` page.\n4. Open the network section of your browser's developer tools.\n5. Click on the `bq_poc` system's meatball menu and then click edit.\n6. 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.\n\n```json\n{\n  \"secrets\": {\n    \"keyfile_creds\": {\n      \"type\": \"value\",\n      \"project_id\": \"value\",\n      \"private_key_id\": \"value\",\n      \"private_key\": \"value\",\n      \"client_email\": \"value\",\n      \"client_id\": \"value\",\n      \"auth_uri\": \"value\",\n      \"token_uri\": \"value\",\n      \"auth_provider_x509_cert_url\": \"value\",\n      \"client_x509_cert_url\": \"value\"\n    }\n  }\n}\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "ethyca-fides"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.37.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ethyca/fides/security/advisories/GHSA-rcvg-jj3g-rj7c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-35189"
  }, {
    "type" : "WEB",
    "url" : "https://cloud.google.com/iam/docs/key-rotation"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ethyca/fides"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-02T22:28:03Z",
    "nvd_published_at" : "2024-05-30T20:15:09Z"
  }
}