🛡️ CVE-2022-23628 — open-policy-agent
Description
Incorrect Calculation in github.com/open-policy-agent/opa
Impact
Under certain conditions, pretty-printing an AST that contains synthetic nodes could change the logic of some statements by reordering array literals. Example of policies impacted are those that parse and compare web paths, see the example below.
All of these three conditions have to be met to create an adverse effect:
1. An AST of Rego had to be created programmatically such that it ends up containing terms without a location (such as wildcard variables).
2. The AST had to be pretty-printed using the github.com/open-policy-agent/opa/format package.
3. The result of the pretty-printing had to be parsed and evaluated again via an OPA instance using the bundles, or the Golang packages.
If any of these three conditions are not met, you are not affected.
Notably, all three would be true if using optimized bundles, i.e. bundles created with opa build -O=1 or higher.
In that case, the optimizer would fulfil condition (1.), the result of that would be pretty-printed when writing the bundle to disk, fulfilling (2.). When the bundle was then used, we'd satisfy (3.).
Example
For example, the process outlined above could turn
this rule
```rego
hello {
["foo", _] = split(input.resource, "/")
}
```
into
```rego
hello {
[_, "foo"] = split(input.resource, "/")
}
```
with an input of
```rego
{
"resource": "foo/bar"
}
```
the result would change from
```rego
{
"hello": true
}
```
to (no default value of hello)
```rego
{}
```
The severity was determined to be *moderate* because the conditions are quite particular. Please note that its only the OPA bundle build process thats affected. An OPA sidecar of version 0.36.0 with an optimized bundle built by OPA 0.32.1 would not face this bug.
Patches
Fixed in version 0.37.2.
Workarounds
- Disabling optimization when creating bundles.
References
- Introduced in https://github.com/open-policy-agent/opa/pull/3851
- Backported for the 0.33.1 patch release: https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717
- Fixed by https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239 and https://github.com/open-policy-agent/opa/commit/2bd8edab9e10e2dc9cf76ae8335ced0c224f3055
For more information
If you have any questions or comments about this advisory:
- Open an issue in [Community Discussions](https://github.com/open-policy-agent/community/discussions/categories/opa-and-rego)
- Ask in Slack: https://slack.openpolicyagent.org/
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability low.
Affected software
CVE-2022-23628 is recorded against 2 packages.
- github.com/open-policy-agent/opa
- open-policy-agent (from 0.33.1 up to 0.37.0)
Timeline and source
Published on 9 February 2022 and last revised on 20 May 2024. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Package)
pkg.go.dev (Web)
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| github.com/open-policy-agent/opa | — | — |
| open-policy-agent | 0.33.1 | 0.37.0 |
References
Similar Threats
- High CVE-2026-26205
- High CVE-2025-46569
- Medium CVE-2024-8260
- High CVE-2022-36085
- High CVE-2022-33082
More CVE 2022 advisories
Browse all of CVE 2022 in the advisory index.
Vulnerability Monitoring
Track new vulnerabilities in open-policy-agent
CVE-2022-23628 is rated CVSS 6.3 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.