CVE-2024-7594 Affecting vault-fips-1.17 package, versions <1.17.6-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-VAULTFIPS117-8352764
  • published7 Nov 2024
  • disclosed26 Sept 2024

Introduced: 26 Sep 2024

CVE-2024-7594  (opens in a new tab)

How to fix?

Upgrade Chainguard vault-fips-1.17 to version 1.17.6-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vault-fips-1.17 package and not the vault-fips-1.17 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vault’s SSH secrets engine could be used to authenticate as any user on the host. Fixed in Vault Community Edition 1.17.6, and in Vault Enterprise 1.17.6, 1.16.10, and 1.15.15.