chore(deps): bump the go_modules group across 1 directory with 3 updates

[dependabot]

Bumps the go_modules group with 3 updates in the / directory: github.com/open-policy-agent/opa, github.com/docker/docker and github.com/golang-jwt/jwt/v4.

Updates github.com/open-policy-agent/opa from 0.63.0 to 0.68.0

Release notes

Sourced from github.com/open-policy-agent/opa's releases.

v0.68.0

This release contains a mix of features and bugfixes.

Breaking Changes

entrypoint annotation implies document scope (#6798)

The entrypoint annotation's scope requirement has changed from rule to document (open-policy-agent/opa#6798). Furthermore, if no scope annotation is declared for a METADATA block preceding a rule, the presence of an entrypoint annotation with a true value will assign the block a document scope, where the rule scope is otherwise the default.

In practice, a rule entrypoint always point to the entire document and not a particular rule definition. The previous behavior was a bug, and one we've now addressed.

Authored by @​anderseknert

Topdown and Rego

• ast: Fixing nil-pointer dereference in compiler for partial rule edge case (#6930) authored by @​johanfylling
• ast+parser: Add hint to future-proof imports (6968) authored by @​srenatus
• topdown: Adding unification scope to virtual-cache key. Fixing issue where false positive cache hits can occur when unification "restricts" the scope of ref-head rule evaluation (#6926) authored by @​johanfylling reported by @​anderseknert
• topdown: Marshal JWT encode sign inputs as JSON (#6934) authored by @​charlieegan3

Runtime, Tooling, SDK

• ast: Make type checker copy method copy all values (#6949) authored by @​anderseknert
• ast: Include term locations in rule heads when requested (#6860) authored by @​anderseknert
• debug: Adding experimental debugger SDK (#6876) authored by @​johanfylling
• distributedtracing: allow OpenTelemetry resource attributes to be configured under distributed_tracing config (#6942) authored and reported by @​brettmc
• download: Fixing issue when saving OCI bundles on disk (#6939) authored and reported by @​Sergey-Kizimov
• logging: Always include HTTP request context in incoming req context (#6951) authored by @​ashutosh-narkar reported by @​alvarogomez93
• plugins/bundle: Avoid race-condition during bundle reconfiguration and activation (#6849) authored by @​ashutosh-narkar reported by @​Pushpalanka
• plugins/bundle: Escape reserved chars used in persisted bundle directory name (#6915) authored by @​ashutosh-narkar reported by @​alvarogomez93
• plugins/rest: Support AWS_CONTAINER_CREDENTIALS_FULL_URI metadata endpoint (#6893) authored and reported by @​mbamber
• util+server: Fix bug around chunked request handling. (#6904) authored by @​philipaconrad reported by @​David-Wobrock
• opa exec: This command never supported "pretty" formatting (--format=pretty or -f pretty), only json. Passing pretty is now invalid. (#6923) authored by @​srenatus Note that the flag is now unnecessary, but it's kept so existing calls like opa exec -fjson ... remain valid.

Security Fix: CVE-2024-8260 (#6933)

This release includes a fix where OPA would accept UNC locations on Windows. Reading those could leak NTLM hashes. The attack vector would include an adversary tricking the user in passing an UNC path to OPA, e.g. opa eval -d $FILE. UNC paths are now forbidden. If this is an issue for you, please reach out on Slack or GitHub issues.

Reported by Shelly Raban Authored by @​ashutosh-narkar

Docs, Website, Ecosystem

• docs: Suggest using opa-config.yaml as name for config file (#6966) (#6959) authored by @​anderseknert
• docs: Add documentation for OPA Spring Boot integration (#6898) authored by @​charlieegan3
• docs: Update Istio tutorial (#6896) authored by @​Pindar
• docs: Update contrib docs (#6974) authored by @​charlieegan3

... (truncated)

Changelog

Sourced from github.com/open-policy-agent/opa's changelog.

0.68.0

This release contains a mix of features and bugfixes.

Breaking Changes

entrypoint annotation implies document scope (#6798)

The entrypoint annotation's scope requirement has changed from rule to document (open-policy-agent/opa#6798). Furthermore, if no scope annotation is declared for a METADATA block preceding a rule, the presence of an entrypoint annotation with a true value will assign the block a document scope, where the rule scope is otherwise the default.

In practice, a rule entrypoint always point to the entire document and not a particular rule definition. The previous behavior was a bug, and one we've now addressed.

Authored by @​anderseknert

Topdown and Rego

• ast: Fixing nil-pointer dereference in compiler for partial rule edge case (#6930) authored by @​johanfylling
• ast+parser: Add hint to future-proof imports (6968) authored by @​srenatus
• topdown: Adding unification scope to virtual-cache key. Fixing issue where false positive cache hits can occur when unification "restricts" the scope of ref-head rule evaluation (#6926) authored by @​johanfylling reported by @​anderseknert
• topdown: Marshal JWT encode sign inputs as JSON (#6934) authored by @​charlieegan3

Runtime, Tooling, SDK

• ast: Make type checker copy method copy all values (#6949) authored by @​anderseknert
• ast: Include term locations in rule heads when requested (#6860) authored by @​anderseknert
• debug: Adding experimental debugger SDK (#6876) authored by @​johanfylling
• distributedtracing: allow OpenTelemetry resource attributes to be configured under distributed_tracing config (#6942) authored and reported by @​brettmc
• download: Fixing issue when saving OCI bundles on disk (#6939) authored and reported by @​Sergey-Kizimov
• logging: Always include HTTP request context in incoming req context (#6951) authored by @​ashutosh-narkar reported by @​alvarogomez93
• plugins/bundle: Avoid race-condition during bundle reconfiguration and activation (#6849) authored by @​ashutosh-narkar reported by @​Pushpalanka
• plugins/bundle: Escape reserved chars used in persisted bundle directory name (#6915) authored by @​ashutosh-narkar reported by @​alvarogomez93
• plugins/rest: Support AWS_CONTAINER_CREDENTIALS_FULL_URI metadata endpoint (#6893) authored and reported by @​mbamber
• util+server: Fix bug around chunked request handling. (#6904) authored by @​philipaconrad reported by @​David-Wobrock
• opa exec: This command never supported "pretty" formatting (--format=pretty� or -f pretty), only json. Passing pretty is now invalid. (#6923) authored by @​srenatus Note that the flag is now unnecessary, but it's kept so existing calls like opa exec -fjson ... remain valid.

Security Fix: CVE-2024-8260 (#6933)

This release includes a fix where OPA would accept UNC locations on Windows. Reading those could leak NTLM hashes. The attack vector would include an adversary tricking the user in passing an UNC path to OPA, e.g. opa eval -d $FILE. UNC paths are now forbidden. If this is an issue for you, please reach out on Slack or GitHub issues.

Reported by Shelly Raban Authored by @​ashutosh-narkar

Docs, Website, Ecosystem

... (truncated)

Commits

• db53d77 Prepare v0.68.0 release (#6976)
• 2d28934 build(deps): bump github/codeql-action from 3.26.5 to 3.26.6
• 1bec88c docs: Update contrib docs (#6974)
• 3ac5104 debug: Adding debugger SDK (#6877)
• b0f417f build(deps): bump github.com/prometheus/client_golang from 1.20.1 to 1.20.2
• d613fd1 build(deps): bump google.golang.org/grpc from 1.65.0 to 1.66.0 (#6971)
• f10cc1f Change required scope of entrypoint from rule to document (#6963)
• 5d08783 topdown: Adding unification scope to virtual-cache key
• 25d21f5 ast/parser: add hint to future-proof imports (#6968)
• 7b535a7 Docs: suggest using opa-config.yaml as name for config file (#6966)
• Additional commits viewable in compare view

Updates github.com/docker/docker from 24.0.9+incompatible to 25.0.6+incompatible

Release notes

Sourced from github.com/docker/docker's releases.

v25.0.6

25.0.6

For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:

• docker/cli, 25.0.6 milestone
• moby/moby, 25.0.6 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

Security

This release contains a fix for CVE-2024-41110 / GHSA-v23v-6jw2-98fq that impacted setups using authorization plugins (AuthZ) for access control.

Bug fixes and enhancements

• [25.0] remove erroneous platform from image config OCI descriptor in docker save output. moby/moby#47695
• [25.0 backport] Fix a nil dereference when getting image history for images having layers without the Created value set. moby/moby#47759
• [25.0 backport] apparmor: Allow confined runc to kill containers. moby/moby#47830
• [25.0 backport] Fix an issue where rapidly promoting a Swarm node after another node was demoted could cause the promoted node to fail its promotion. moby/moby#47869
• [25.0 backport] don't depend on containerd platform.Parse to return a typed error. moby/moby#47890
• [25.0 backport] builder/mobyexporter: Add missing nil check moby/moby#47987

Packaging updates

• Update AWS SDK Go v2 to v1.24.1 for AWS CloudWatch logging driver. moby/moby#47724
• Update Go runtime to 1.21.12, which contains security fixes for CVE-2024-24791 moby/moby#48146
• Update Containerd (static binaries only) to v1.7.20. moby/moby#48199

Full Changelog: moby/moby@v25.0.5...v25.0.6

v25.0.5

25.0.5

For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:

• docker/cli, 25.0.5 milestone
• moby/moby, 25.0.5 milestone
• Deprecated and removed features, see Deprecated Features.
• Changes to the Engine API, see API version history.

Security

This release contains a security fix for CVE-2024-29018, a potential data exfiltration from 'internal' networks via authoritative DNS servers.

Bug fixes and enhancements

• CVE-2024-29018: Do not forward requests to external DNS servers for a container that is only connected to an 'internal' network. Previously, requests were forwarded if the host's DNS server was running on a loopback address, like systemd's 127.0.0.53. moby/moby#47589

• plugin: fix mounting /etc/hosts when running in UserNS. moby/moby#47588

• rootless: fix open /etc/docker/plugins: permission denied. moby/moby#47587

• Fix multiple parallel docker build runs leaking disk space. moby/moby#47527

... (truncated)

Commits

• b08a51f Merge pull request #48231 from austinvazquez/backport-vendor-otel-v0.46.1-to-...
• d151b0f vendor: OTEL v0.46.1 / v1.21.0
• c6ba9a5 Merge pull request #48225 from austinvazquez/backport-workflow-artifact-reten...
• 4673a3c Merge pull request #48227 from austinvazquez/backport-backport-branch-check-t...
• 30f8908 github/ci: Check if backport is opened against the expected branch
• 7454d6a ci: update workflow artifacts retention
• 65cc597 Merge commit from fork
• b722836 Merge pull request #48199 from austinvazquez/update-containerd-binary-to-1.7.20
• e8ecb9c update containerd binary to v1.7.20
• e6cae1f update containerd binary to v1.7.19
• Additional commits viewable in compare view

Updates github.com/golang-jwt/jwt/v4 from 4.5.0 to 4.5.1

Release notes

Sourced from github.com/golang-jwt/jwt/v4's releases.

v4.5.1

Security

Unclear documentation of the error behavior in ParseWithClaims in <= 4.5.0 could lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by ParseWithClaims return both error codes. If users only check for the jwt.ErrTokenExpired using error.Is, they will ignore the embedded jwt.ErrTokenSignatureInvalid and thus potentially accept invalid tokens.

This issue was documented in GHSA-29wx-vh33-7x7r and fixed in this release.

Note: v5 was not affected by this issue. So upgrading to this release version is also recommended.

What's Changed

• Back-ported error-handling logic in ParseWithClaims from v5 branch. This fixes GHSA-29wx-vh33-7x7r.

Full Changelog: golang-jwt/jwt@v4.5.0...v4.5.1

Commits

• 7b1c1c0 Merge commit from fork
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.