CVE-2022-23628: Github.com/open policy agent/opa Incorrect Calculation Vulnerability

MODERATE
Advisory Identifier: GHSA-hcw3-j74m-qc58
CVSS 6.3
CWE-682
Published
Advisory Summary

CVE-2022-23628 is a MODERATE (CVSS 6.3) incorrect calculation vulnerability (CWE-682: Incorrect Calculation) affecting Github.com/open policy agent/opa libraries in the Go ecosystem. The issue involves incorrect calculation in github.com/open-policy-agent/opa. Remediation is available by upgrading affected packages to version 0.37.2.

CVE-2022-23628 at a Glance

CVE Identifier CVE-2022-23628
GHSA Identifier GHSA-hcw3-j74m-qc58
Severity MODERATE
CVSS v3.1 Base Score 6.3
CWE Classification CWE-682: Incorrect Calculation
Affected Product Github.com/open policy agent/opa
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2022-23628

To remediate this vulnerability, upgrade all affected Github.com/open policy agent/opa dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/open-policy-agent/opa fixed: 0.37.2
Upgrade github.com/open-policy-agent/opa to 0.37.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/open-policy-agent/opa

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-23628, inspect your project dependencies for Github.com/open policy agent/opa:

inspect dependencies for github.com/open-policy-agent/opa

Analyze the terminal output to locate any version of Github.com/open policy agent/opa in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.37.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-682: Incorrect Calculation, where the product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management. In Github.com/open policy agent/opa, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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/

CVE-2022-23628 Affected Github.com/open policy agent/opa Versions

1 component(s)
Fixed Versions:
0.37.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/open-policy-agent/opa
Go
≥ 0.33.1
< 0.37.2
0.37.2

References

Frequently Asked Questions

What is CVE-2022-23628?
CVE-2022-23628 is a security vulnerability in Github.com/open policy agent/opa involving Incorrect Calculation in github.com/open-policy-agent/opa under CWE-682: Incorrect Calculation.
Which Github.com/open policy agent/opa versions are affected?
Affected versions include releases prior to 0.37.2 across affected packages: github.com/open-policy-agent/opa.
What version fixes CVE-2022-23628?
Upgrading to 0.37.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/open-policy-agent/opa affected?
Yes, github.com/open-policy-agent/opa is affected in releases prior to 0.37.2. Upgrade your dependency to 0.37.2 or later.
What is the CVSS score of CVE-2022-23628?
CVE-2022-23628 has a CVSS v3.1 base score of 6.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L.
What CWE is associated with CVE-2022-23628?
CVE-2022-23628 is classified under CWE-682: Incorrect Calculation (The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.).
How can I check Go dependencies for CVE-2022-23628?
Run the dependency tree command: 'inspect dependencies for github.com/open-policy-agent/opa'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hcw3-j74m-qc58",
  "modified" : "2024-05-20T20:41:41Z",
  "published" : "2022-02-09T22:17:37Z",
  "aliases" : [ "CVE-2022-23628" ],
  "summary" : "Incorrect Calculation in github.com/open-policy-agent/opa",
  "details" : "### Impact\n\nUnder 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.\n\n**All of these** three conditions have to be met to create an adverse effect:\n\n1. An AST of Rego had to be **created programmatically** such that it ends up containing terms without a location (such as wildcard variables).\n2. The AST had to be **pretty-printed** using the `github.com/open-policy-agent/opa/format` package.\n3. The result of the pretty-printing had to be **parsed and evaluated again** via an OPA instance using the bundles, or the Golang packages.\n\nIf any of these three conditions are not met, you are not affected.\n\nNotably, all three would be true if using **optimized bundles**, i.e. bundles created with `opa build -O=1` or higher.\nIn 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.).\n\n#### Example\nFor example, the process outlined above could turn \nthis rule\n```rego\nhello {\n\t[\"foo\", _] = split(input.resource, \"/\")\n}\n```\n\ninto\n```rego\nhello {\n\t[_, \"foo\"] = split(input.resource, \"/\")\n}\n```\n\nwith an input of\n```rego\n{\n    \"resource\": \"foo/bar\"\n}\n```\n\nthe result would change from\n```rego\n{\n    \"hello\": true\n}\n```\nto (no default value of hello)\n```rego\n{}\n```\n\nThe 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.\n\n### Patches\n\nFixed in version 0.37.2.\n\n### Workarounds\n\n- Disabling optimization when creating bundles.\n\n### References\n\n- Introduced in https://github.com/open-policy-agent/opa/pull/3851\n- Backported for the 0.33.1 patch release: https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717\n- Fixed by https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239 and https://github.com/open-policy-agent/opa/commit/2bd8edab9e10e2dc9cf76ae8335ced0c224f3055\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [Community Discussions](https://github.com/open-policy-agent/community/discussions/categories/opa-and-rego)\n* Ask in Slack: https://slack.openpolicyagent.org/",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/open-policy-agent/opa"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.33.1"
      }, {
        "fixed" : "0.37.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-policy-agent/opa/security/advisories/GHSA-hcw3-j74m-qc58"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-23628"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-policy-agent/opa/pull/3851"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-policy-agent/opa/commit/2bd8edab9e10e2dc9cf76ae8335ced0c224f3055"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-policy-agent/opa"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2022-0316"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-682" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-02-09T22:17:37Z",
    "nvd_published_at" : "2022-02-09T22:15:00Z"
  }
}