CVE-2023-46124

Fides Server-Side Request Forgery Vulnerability in Custom Integration Upload

Workarounds

There are no workarounds.

The Fides web application allows a custom integration to be uploaded as a ZIP file containing configuration and dataset definitions in YAML format.

It was discovered that specially crafted YAML dataset and config files allow a malicious user to perform arbitrary requests to internal systems and exfiltrate data outside the environment (also known as a Server-Side Request Forgery). The application does not perform proper validation to block attempts to connect to internal (including localhost) resources.

Exploitation is limited to API clients with the CONNECTOR_TEMPLATE_REGISTER authorization scope. In the Fides Admin UI this scope is restricted to highly privileged users, specifically root users and users with the owner role.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2023-46124 has a CVSS score of 8.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.22.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The vulnerability has been patched in Fides version 2.22.1. Users are advised to upgrade to this version or later to secure their systems against this threat.

1. What is CVE-2023-46124? CVE-2023-46124 is a high-severity server-side request forgery (SSRF) vulnerability in ethyca-fides (pip), affecting versions < 2.22.1. It is fixed in 2.22.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2023-46124? CVE-2023-46124 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ethyca-fides are affected by CVE-2023-46124? ethyca-fides (pip) versions < 2.22.1 is affected.
4. Is there a fix for CVE-2023-46124? Yes. CVE-2023-46124 is fixed in 2.22.1. Upgrade to this version or later.
5. Is CVE-2023-46124 exploitable, and should I be worried? Whether CVE-2023-46124 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-46124 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-46124? Upgrade ethyca-fides to 2.22.1 or later.

Other vulnerabilities in ethyca-fides