2.59.1
2 years ago
5 days ago
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 freeVulnerability | Vulnerable Version |
---|---|
ethyca-fides is an Open-source ecosystem for data privacy as code. Affected versions of this package are vulnerable to Client-Side Enforcement of Server-Side Security due to improper implementation of password policy validations in the How to fix Client-Side Enforcement of Server-Side Security? Upgrade | [,2.50.0rc0) |
ethyca-fides is an Open-source ecosystem for data privacy as code. Affected versions of this package are vulnerable to Timing Attack due to the discrepancy in response times between valid and invalid usernames in the login endpoint. An attacker can determine the existence of valid usernames by analyzing the time it takes for the server to respond to login requests. By exploiting this vulnerability, an attacker can enumerate users on the system. How to fix Timing Attack? Upgrade | [,2.44.0) |
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 How to fix Information Exposure Through an Error Message? Upgrade | [,2.37.0) |
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 | [,2.37.0) |
ethyca-fides is an Open-source ecosystem for data privacy as code. Affected versions of this package are vulnerable to Race Condition during the initialization of the FidesConfig class. This vulnerability can lead to unexpected behavior or incorrect security configurations if two threads attempt to modify the security attribute simultaneously. How to fix Race Condition? Upgrade | [,2.1.0) |
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 How to fix Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)? Upgrade | [,2.24.0) |
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 Note:
This is only exploitable if the API client has the How to fix Server-side Request Forgery (SSRF)? Upgrade | [,2.22.1) |
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 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 | [,2.22.1) |
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 Note: This exploitation is limited to Admin UI users with the contributor role or higher. How to fix Cross-site Scripting (XSS)? Upgrade | [,2.22.1) |
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 How to fix Directory Traversal? Upgrade | [,2.15.1) |