CVE-2024-7594 (GCVE-0-2024-7594)
Vulnerability from cvelistv5
Published
2024-09-26 19:52
Modified
2025-01-10 13:06
Summary
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.
Impacted products
Vendor Product Version
HashiCorp Vault Version: 1.7.7   
Create a notification for this product.
   HashiCorp Vault Enterprise Version: 1.7.7   
Create a notification for this product.
Show details on NVD website


{
   containers: {
      adp: [
         {
            affected: [
               {
                  cpes: [
                     "cpe:2.3:a:hashicorp:vault_enterprise:*:*:*:*:*:*:*:*",
                  ],
                  defaultStatus: "unknown",
                  product: "vault_enterprise",
                  vendor: "hashicorp",
                  versions: [
                     {
                        lessThan: "1.17.6",
                        status: "affected",
                        version: "1.7.7",
                        versionType: "semver",
                     },
                     {
                        status: "affected",
                        version: "1.16.9",
                     },
                     {
                        status: "affected",
                        version: "1.15.14",
                     },
                  ],
               },
               {
                  cpes: [
                     "cpe:2.3:a:hashicorp:vault_community_edition:*:*:*:*:*:*:*:*",
                  ],
                  defaultStatus: "unknown",
                  product: "vault_community_edition",
                  vendor: "hashicorp",
                  versions: [
                     {
                        lessThan: "1.17.6",
                        status: "affected",
                        version: "1.7.7",
                        versionType: "semver",
                     },
                  ],
               },
            ],
            metrics: [
               {
                  other: {
                     content: {
                        id: "CVE-2024-7594",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "total",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-09-26T20:24:40.797176Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-09-26T20:29:58.984Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
         {
            providerMetadata: {
               dateUpdated: "2025-01-10T13:06:49.543Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  url: "https://security.netapp.com/advisory/ntap-20250110-0007/",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               platforms: [
                  "64 bit",
                  "32 bit",
                  "x86",
                  "ARM",
                  "MacOS",
                  "Windows",
                  "Linux",
               ],
               product: "Vault",
               repo: "https://github.com/hashicorp/vault",
               vendor: "HashiCorp",
               versions: [
                  {
                     lessThan: "1.17.6",
                     status: "affected",
                     version: "1.7.7",
                     versionType: "semver",
                  },
               ],
            },
            {
               defaultStatus: "unaffected",
               platforms: [
                  "64 bit",
                  "32 bit",
                  "x86",
                  "ARM",
                  "MacOS",
                  "Windows",
                  "Linux",
               ],
               product: "Vault Enterprise",
               repo: "https://github.com/hashicorp/vault",
               vendor: "HashiCorp",
               versions: [
                  {
                     changes: [
                        {
                           at: "1.16.10",
                           status: "unaffected",
                        },
                        {
                           at: "1.15.15",
                           status: "unaffected",
                        },
                     ],
                     lessThan: "1.17.6",
                     status: "affected",
                     version: "1.7.7",
                     versionType: "semver",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "<p>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.</p><br/>",
                  },
               ],
               value: "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.",
            },
         ],
         impacts: [
            {
               capecId: "CAPEC-1",
               descriptions: [
                  {
                     lang: "en",
                     value: "CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs",
                  },
               ],
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  baseScore: 7.5,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
                  version: "3.1",
               },
               format: "CVSS",
               scenarios: [
                  {
                     lang: "en",
                     value: "GENERAL",
                  },
               ],
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-732",
                     description: "CWE-732: Incorrect Permission Assignment for Critical Resource",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-09-26T19:56:15.934Z",
            orgId: "67fedba0-ff2e-4543-ba5b-aa93e87718cc",
            shortName: "HashiCorp",
         },
         references: [
            {
               url: "https://discuss.hashicorp.com/t/hcsec-2024-20-vault-ssh-secrets-engine-configuration-did-not-restrict-valid-principals-by-default/70251",
            },
         ],
         source: {
            advisory: "HCSEC-2024-20",
            discovery: "EXTERNAL",
         },
         title: "Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default",
      },
   },
   cveMetadata: {
      assignerOrgId: "67fedba0-ff2e-4543-ba5b-aa93e87718cc",
      assignerShortName: "HashiCorp",
      cveId: "CVE-2024-7594",
      datePublished: "2024-09-26T19:52:55.652Z",
      dateReserved: "2024-08-07T17:46:31.343Z",
      dateUpdated: "2025-01-10T13:06:49.543Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         descriptions: "[{\"lang\": \"en\", \"value\": \"Vault\\u2019s 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\\u2019s 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.\"}, {\"lang\": \"es\", \"value\": \"El motor de secretos SSH de Vault no requer\\u00eda que la lista valid_principals contuviera un valor de manera predeterminada. Si los campos valid_principals y default_user de la configuraci\\u00f3n del motor de secretos SSH no est\\u00e1n configurados, un certificado SSH solicitado por un usuario autorizado al motor de secretos SSH de Vault podr\\u00eda usarse para autenticarse como cualquier usuario en el host. Se corrigi\\u00f3 en Vault Community Edition 1.17.6 y en Vault Enterprise 1.17.6, 1.16.10 y 1.15.15.\"}]",
         id: "CVE-2024-7594",
         lastModified: "2025-01-10T13:15:10.303",
         metrics: "{\"cvssMetricV31\": [{\"source\": \"security@hashicorp.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.6, \"impactScore\": 5.9}]}",
         published: "2024-09-26T20:15:07.687",
         references: "[{\"url\": \"https://discuss.hashicorp.com/t/hcsec-2024-20-vault-ssh-secrets-engine-configuration-did-not-restrict-valid-principals-by-default/70251\", \"source\": \"security@hashicorp.com\"}, {\"url\": \"https://security.netapp.com/advisory/ntap-20250110-0007/\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
         sourceIdentifier: "security@hashicorp.com",
         vulnStatus: "Awaiting Analysis",
         weaknesses: "[{\"source\": \"security@hashicorp.com\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-732\"}]}]",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2024-7594\",\"sourceIdentifier\":\"security@hashicorp.com\",\"published\":\"2024-09-26T20:15:07.687\",\"lastModified\":\"2025-01-10T13:15:10.303\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\"},{\"lang\":\"es\",\"value\":\"El motor de secretos SSH de Vault no requería que la lista valid_principals contuviera un valor de manera predeterminada. Si los campos valid_principals y default_user de la configuración del motor de secretos SSH no están configurados, un certificado SSH solicitado por un usuario autorizado al motor de secretos SSH de Vault podría usarse para autenticarse como cualquier usuario en el host. Se corrigió en Vault Community Edition 1.17.6 y en Vault Enterprise 1.17.6, 1.16.10 y 1.15.15.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security@hashicorp.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.6,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"security@hashicorp.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-732\"}]}],\"references\":[{\"url\":\"https://discuss.hashicorp.com/t/hcsec-2024-20-vault-ssh-secrets-engine-configuration-did-not-restrict-valid-principals-by-default/70251\",\"source\":\"security@hashicorp.com\"},{\"url\":\"https://security.netapp.com/advisory/ntap-20250110-0007/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://security.netapp.com/advisory/ntap-20250110-0007/\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-01-10T13:06:49.543Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-7594\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-26T20:24:40.797176Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:hashicorp:vault_enterprise:*:*:*:*:*:*:*:*\"], \"vendor\": \"hashicorp\", \"product\": \"vault_enterprise\", \"versions\": [{\"status\": \"affected\", \"version\": \"1.7.7\", \"lessThan\": \"1.17.6\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"1.16.9\"}, {\"status\": \"affected\", \"version\": \"1.15.14\"}], \"defaultStatus\": \"unknown\"}, {\"cpes\": [\"cpe:2.3:a:hashicorp:vault_community_edition:*:*:*:*:*:*:*:*\"], \"vendor\": \"hashicorp\", \"product\": \"vault_community_edition\", \"versions\": [{\"status\": \"affected\", \"version\": \"1.7.7\", \"lessThan\": \"1.17.6\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unknown\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-26T20:27:27.031Z\"}}], \"cna\": {\"title\": \"Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default\", \"source\": {\"advisory\": \"HCSEC-2024-20\", \"discovery\": \"EXTERNAL\"}, \"impacts\": [{\"capecId\": \"CAPEC-1\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/hashicorp/vault\", \"vendor\": \"HashiCorp\", \"product\": \"Vault\", \"versions\": [{\"status\": \"affected\", \"version\": \"1.7.7\", \"lessThan\": \"1.17.6\", \"versionType\": \"semver\"}], \"platforms\": [\"64 bit\", \"32 bit\", \"x86\", \"ARM\", \"MacOS\", \"Windows\", \"Linux\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://github.com/hashicorp/vault\", \"vendor\": \"HashiCorp\", \"product\": \"Vault Enterprise\", \"versions\": [{\"status\": \"affected\", \"changes\": [{\"at\": \"1.16.10\", \"status\": \"unaffected\"}, {\"at\": \"1.15.15\", \"status\": \"unaffected\"}], \"version\": \"1.7.7\", \"lessThan\": \"1.17.6\", \"versionType\": \"semver\"}], \"platforms\": [\"64 bit\", \"32 bit\", \"x86\", \"ARM\", \"MacOS\", \"Windows\", \"Linux\"], \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://discuss.hashicorp.com/t/hcsec-2024-20-vault-ssh-secrets-engine-configuration-did-not-restrict-valid-principals-by-default/70251\"}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"Vault\\u2019s 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\\u2019s 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.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"<p>Vault\\u2019s 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\\u2019s 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.</p><br/>\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-732\", \"description\": \"CWE-732: Incorrect Permission Assignment for Critical Resource\"}]}], \"providerMetadata\": {\"orgId\": \"67fedba0-ff2e-4543-ba5b-aa93e87718cc\", \"shortName\": \"HashiCorp\", \"dateUpdated\": \"2024-09-26T19:56:15.934Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2024-7594\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-01-10T13:06:49.543Z\", \"dateReserved\": \"2024-08-07T17:46:31.343Z\", \"assignerOrgId\": \"67fedba0-ff2e-4543-ba5b-aa93e87718cc\", \"datePublished\": \"2024-09-26T19:52:55.652Z\", \"assignerShortName\": \"HashiCorp\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.