ethyca-fides@2.13.1b2 vulnerabilities

Open-source ecosystem for data privacy as code.

Direct Vulnerabilities

Known vulnerabilities in the ethyca-fides package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Information Exposure Through an Error Message

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Information Exposure Through an Error Message due to a flaw in the internal function handling sensitive annotations, which fails to mask nested sensitive fields properly. An attacker can access sensitive data such as private keys by exploiting this vulnerability in the API endpoint exposure. This is only exploitable if the BigQuery connection configuration secrets are used, as other connection types with non-nested sensitive fields are not affected.

How to fix Information Exposure Through an Error Message?

Upgrade ethyca-fides to version 2.37.0 or higher.

[,2.37.0)
  • L
Insertion of Sensitive Information into Log File

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to improper escaping of the password string in the webserver configuration. An attacker can access part of the database password by examining error logs where this information is inadvertently logged.

How to fix Insertion of Sensitive Information into Log File?

Upgrade ethyca-fides to version 2.37.0 or higher.

[,2.37.0)
  • H
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) when the subject_identity_verification_required function is enabled. An attacker can predict all future one-time code values during the lifetime of the backend python process by generating several hundred consecutive one-time codes. This allows the attacker to submit a verified data erasure request, resulting in deletion of data for the targeted user and submit a verified consent request, modifying a user's privacy preferences. This is only exploitable if subject_identity_verification_required in the [execution] section of fides.toml or the env var FIDES__EXECUTION__SUBJECT_IDENTITY_VERIFICATION_REQUIRED is set to True on the fides webserver backend.

How to fix Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)?

Upgrade ethyca-fides to version 2.24.0 or higher.

[,2.24.0)
  • M
Server-side Request Forgery (SSRF)

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the saas_util.py and authenticated_client.py files. An attacker can perform arbitrary requests to internal systems and exfiltrate data outside the environment by uploading specially crafted YAML dataset and config files.

Note: This is only exploitable if the API client has the CONNECTOR_TEMPLATE_REGISTER authorization scope, which is typically restricted to highly privileged users such as root users and users with the owner role.

How to fix Server-side Request Forgery (SSRF)?

Upgrade ethyca-fides to version 2.22.1 or higher.

[,2.22.1)
  • M
Information Exposure Through Sent Data

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Information Exposure Through Sent Data via the api/v1/config endpoint. An attacker can retrieve sensitive configuration information, by exploiting the API.

Note: This is only exploitable if the user has roles lower than the owner role, such as the viewer role.

How to fix Information Exposure Through Sent Data?

Upgrade ethyca-fides to version 2.22.1 or higher.

[,2.22.1)
  • M
Cross-site Scripting (XSS)

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in src/fides/api/schemas/privacy_experience.py. An attacker can trigger JavaScript execution on an integrated website by crafting a payload in the privacy policy URL.

Note:

This exploitation is limited to Admin UI users with the contributor role or higher.

How to fix Cross-site Scripting (XSS)?

Upgrade ethyca-fides to version 2.22.1 or higher.

[,2.22.1)
  • H
Remote Code Execution (RCE)

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Remote Code Execution (RCE) in the fides.toml file and the FIDES__SECURITY__ALLOW_CUSTOM_CONNECTOR_FUNCTIONS variable.

Note: Exploitation is only possible if the security configuration parameter allow_custom_connector_functions is enabled by the user deploying the Fides webserver container, either in fides.toml or by setting the env var FIDES__SECURITY__ALLOW_CUSTOM_CONNECTOR_FUNCTIONS=True. By default this configuration parameter is disabled.

How to fix Remote Code Execution (RCE)?

Upgrade ethyca-fides to version 2.19.0 or higher.

[2.11.0,2.19.0)
  • H
Arbitrary Code Execution

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Arbitrary Code Execution when the Fides webserver API is used to upload a ZIP file containing custom Python code. An attacker can execute arbitrary code on the target system within the context of the webserver python process owner on the webserver container, which by default is root, and leverage that access to attack underlying infrastructure and integrated systems by bypassing the sandboxed environment.

Note: This is only exploitable if the security configuration parameter allow_custom_connector_functions is enabled by the user deploying the Fides webserver container, either in fides.toml or by setting the env var FIDES__SECURITY__ALLOW_CUSTOM_CONNECTOR_FUNCTIONS=True.

How to fix Arbitrary Code Execution?

Upgrade ethyca-fides to version 2.19.0 or higher.

[2.11.0,2.19.0)
  • M
Denial of Service (DoS)

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Denial of Service (DoS) due to the save_template() function in connector_registry_service.py accepting uploads of files that could contain a zip bomb. Users with elevated privileges with the CONNECTOR_TEMPLATE_REGISTER scope can exploit this to deny access to all users of the affected server.

How to fix Denial of Service (DoS)?

Upgrade ethyca-fides to version 2.16.0 or higher.

[2.11.0,2.16.0)
  • L
Denial of Service (DoS)

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Denial of Service (DoS) by uploading zip files containing malicious SVG bombs (similar to a billion laughs attack), causing resource exhaustion in Admin UI browser tabs, and creating a persistent denial of service of the 'new connector' page (datastore-connection/new).

Note: Exploitation is limited to users with elevated privileges with the CONNECTOR_TEMPLATE_REGISTER scope, which includes root users and users with the owner role.

How to fix Denial of Service (DoS)?

Upgrade ethyca-fides to version 2.16.0 or higher.

[2.11.0,2.16.0)
  • H
Directory Traversal

ethyca-fides is an Open-source ecosystem for data privacy as code.

Affected versions of this package are vulnerable to Directory Traversal such that it allows remote attackers to access arbitrary files on the fides webserver container's filesystem.

Note:

If the Fides webserver API is not directly accessible to attackers and is instead deployed behind a reverse proxy as recommended in Ethyca's security best practice documentation, and the reverse proxy is an AWS application load balancer, the vulnerability can't be exploited by these attackers. An AWS application load balancer will reject this attack with a 400 error. Additionally, any secrets supplied to the container using environment variables rather than a fides.toml configuration file are not affected by this vulnerability.

How to fix Directory Traversal?

Upgrade ethyca-fides to version 2.15.1 or higher.

[,2.15.1)