Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency hashicorp/nomad to v1.9.6 #10214

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
hashicorp/nomad patch 1.9.5 -> 1.9.6

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

hashicorp/nomad (hashicorp/nomad)

v1.9.6

Compare Source

BREAKING CHANGES:

  • fingerprint: Consul and Vault fingerprints no longer reload periodically [GH-24526]

SECURITY:

  • api: sanitize the SignedIdentities in allocations of events to clean the identity token. [GH-24966]
  • build: Updated Go to 1.23.6 [GH-25041]
  • event stream: fixes vulnerability CVE-2025-0937, where using a wildcard namespace to subscribe to the events API grants a user with "read" capabilites on any namespace, the ability to read events from all namespaces. [GH-25089]

IMPROVEMENTS:

  • auth: adds VerboseLogging option to auth-method config for debugging SSO [GH-24892]
  • cli: Added actions available to a job when running nomad job status command [GH-24959]
  • event stream: adds ability to authenticate using workload identities [GH-24849]
  • services: Nomad service checks now support the tls_skip_verify parameter [GH-24781]
  • task schedule: The task being paused no longer impacts restart attempts [GH-25085]
  • ui: Contextualizes the Start Job button on whether it is startable, revertable, or not [GH-24985]

BUG FIXES:

  • agent: Fixed a bug where Nomad error log messages within syslog showed via the notice priority [GH-24820]
  • agent: Fixed a bug where all syslog entries were marked as notice when using JSON logging format [GH-24865]
  • client: Fixed a bug where temporary RPC errors cause the client to poll for changes more frequently thereafter [GH-25039]
  • csi: Fixed a bug where volume context from the plugin would be erased on volume updates [GH-24922]
  • docker: Fixed a bug that prevented image_pull_timeout from being applied [GH-24991]
  • docker: Fixed a bug where "error reading image pull progress" caused the allocation to get stuck pending [GH-24981]
  • reporting (Enterprise): Updated the reporting metric to utilize node active heartbeat count. [GH-24919]
  • state store: fix for setting correct status for a job version when reverting, and also fixes an issue where jobs were briefly marked dead during restarts [GH-24974]
  • taskrunner: fix panic when a task with dynamic user is recovered [GH-24739]
  • ui: Ensure pending service check blocks are filled [GH-24818]
  • ui: Remove unrequired node read API call when attempting to stream task logs [GH-24973]
  • vault: Fixed a bug where successful renewal was logged as an error [GH-25040]

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/nomad:1.9.6

📦 Image Reference ghcr.io/uniget-org/tools/nomad:1.9.6
digestsha256:2bb2bdd1f9cac9dc6addeafa09cf08d6c9f1f84d30372b04155bf3a96f598166
vulnerabilitiescritical: 0 high: 0 medium: 1 low: 1
platformlinux/amd64
size57 MB
packages301
critical: 0 high: 0 medium: 1 low: 1 github.com/aws/aws-sdk-go 1.55.6 (golang)

pkg:golang/github.com/aws/[email protected]

medium : CVE--2020--8911

Affected range>=0
Fixed versionNot Fixed
Description

A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

low : CVE--2020--8912

Affected range>=0
Fixed versionNot Fixed
Description

A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

Copy link

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/13276394065.

Copy link

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/13276394065.

@github-actions github-actions bot merged commit f0edb81 into main Feb 12, 2025
10 checks passed
@github-actions github-actions bot deleted the renovate/hashicorp-nomad-1.9.x branch February 12, 2025 01:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants