OPA server Data API HTTP path injection of Rego
open-policy-agent opa
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/open-policy-agent/opa/v1/server Go |
|
|
| github.com/open-policy-agent/opa/server Go |
|
|
| github.com/open-policy-agent/opa |
open-policy-agent opa
| Product | Affected | Fixed in |
|---|---|---|
| github.com/open-policy-agent/opa/v1/server Go |
|
|
| github.com/open-policy-agent/opa/server Go |
|
|
| github.com/open-policy-agent/opa |
|
|
Open Policy Agent (OPA) is an open source, general-purpose policy engine. Prior to version 1.4.0, when run as a server, OPA exposes an HTTP Data API for reading and writing documents. Requesting a virtual document through the Data API entails policy evaluation, where a Rego query containing a single data document reference is constructed from the requested path. This query is then used for policy evaluation. A HTTP request path can be crafted in a way that injects Rego code into the constructed query. The evaluation result cannot be made to return any other data than what is generated by the requested path, but this path can be misdirected, and the injected Rego code can be crafted to make the query succeed or fail; opening up for oracle attacks or, given the right circumstances, erroneous policy decision results. Furthermore, the injected code can be crafted to be computationally expensive, resulting in a Denial Of Service (DoS) attack. This issue has been patched in version 1.4.0. A workaround involves having network access to OPA’s RESTful APIs being limited to `localhost` and/or trusted networks, unless necessary for production reasons.
From the CVE record · GitHub_M
Before 1.4.0, OPA running as a server can construct a Rego query from a crafted HTTP Data API path that injects Rego code. An attacker with network access to the API can misdirect the requested path, influence whether the query succeeds or fails, or cause a denial of service through expensive evaluation. Under the right circumstances, this can lead to erroneous policy decisions.
Operators running OPA as a server and users of the affected Go packages github.com/open-policy-agent/opa/v1/server, github.com/open-policy-agent/opa/server, or github.com/open-policy-agent/opa at versions before 1.4.0 should check their deployments.