cve-2024-6468
Vulnerability from cvelistv5
Published
2024-07-11 20:40
Modified
2024-08-01 21:41
Severity ?
EPSS score ?
Summary
Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior
References
Impacted products
▼ | Vendor | Product |
---|---|---|
HashiCorp | Vault | |
HashiCorp | Vault Enterprise |
{ "containers": { "adp": [ { "affected": [ { "cpes": [ "cpe:2.3:a:hashicorp:vault:*:*:*:*:*:*:*:*" ], "defaultStatus": "unknown", "product": "vault", "vendor": "hashicorp", "versions": [ { "lessThan": "1.15.11", "status": "affected", "version": "1.10.0", "versionType": "custom" } ] }, { "cpes": [ "cpe:2.3:a:hashicorp:vault_enterprise:*:*:*:*:*:*:*:*" ], "defaultStatus": "unknown", "product": "vault_enterprise", "vendor": "hashicorp", "versions": [ { "lessThan": "1.15.11", "status": "affected", "version": "1.10.0", "versionType": "custom" } ] } ], "metrics": [ { "other": { "content": { "id": "CVE-2024-6468", "options": [ { "Exploitation": "none" }, { "Automatable": "yes" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2024-07-12T14:14:37.815771Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2024-07-12T14:16:55.605Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" }, { "providerMetadata": { "dateUpdated": "2024-08-01T21:41:03.514Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "x_transferred" ], "url": "https://discuss.hashicorp.com/t/hcsec-2024-14-vault-vulnerable-to-denial-of-service-when-setting-a-proxy-protocol-behavior/68518" } ], "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.15.11", "status": "affected", "version": "1.10.0", "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": [ { "lessThan": "1.15.11", "status": "affected", "version": "1.10.0", "versionType": "semver" } ] } ], "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "\u003cp\u003eVault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.\n\nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.\n\nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.\u003c/p\u003e\u003cbr/\u003e" } ], "value": "Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.\n\nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.\n\nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12." } ], "impacts": [ { "capecId": "CAPEC-469", "descriptions": [ { "lang": "en", "value": "CAPEC-469: HTTP DoS" } ] } ], "metrics": [ { "cvssV3_1": { "baseScore": 7.5, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1" }, "format": "CVSS", "scenarios": [ { "lang": "en", "value": "GENERAL" } ] } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-703", "description": "CWE-703: Improper Check or Handling of Exceptional Conditions", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2024-07-11T20:40:12.298Z", "orgId": "67fedba0-ff2e-4543-ba5b-aa93e87718cc", "shortName": "HashiCorp" }, "references": [ { "url": "https://discuss.hashicorp.com/t/hcsec-2024-14-vault-vulnerable-to-denial-of-service-when-setting-a-proxy-protocol-behavior/68518" } ], "source": { "advisory": "HCSEC-2024-HCSEC-2024-14", "discovery": "INTERNAL" }, "title": "Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior" } }, "cveMetadata": { "assignerOrgId": "67fedba0-ff2e-4543-ba5b-aa93e87718cc", "assignerShortName": "HashiCorp", "cveId": "CVE-2024-6468", "datePublished": "2024-07-11T20:40:12.298Z", "dateReserved": "2024-07-03T03:55:06.235Z", "dateUpdated": "2024-08-01T21:41:03.514Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2024-6468\",\"sourceIdentifier\":\"security@hashicorp.com\",\"published\":\"2024-07-11T21:15:12.910\",\"lastModified\":\"2024-07-12T12:49:11.340\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.\\n\\nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.\\n\\nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.\"},{\"lang\":\"es\",\"value\":\"Vault y Vault Enterprise no manejaron adecuadamente las solicitudes originadas en direcciones IP no autorizadas cuando la opci\u00f3n de escucha TCP, proxy_protocol_behavior, estaba configurada en deny_unauthorized. Al recibir una solicitud de una direcci\u00f3n IP de origen que no figuraba en proxy_protocol_authorized_addrs, el servidor API de Vault se cerraba y ya no respond\u00eda a ninguna solicitud HTTP, lo que podr\u00eda provocar una denegaci\u00f3n de servicio. Si bien este error tambi\u00e9n afect\u00f3 a las versiones de Vault hasta 1.17.1 y 1.16.5, una regresi\u00f3n separada en esas series de versiones no permiti\u00f3 a los operadores de Vault configurar la opci\u00f3n deny_unauthorized, por lo que no permiti\u00f3 que se cumplieran las condiciones para la denegaci\u00f3n de servicio. Corregido en Vault y Vault Enterprise 1.17.2, 1.16.6 y 1.15.12.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security@hashicorp.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"security@hashicorp.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-703\"}]}],\"references\":[{\"url\":\"https://discuss.hashicorp.com/t/hcsec-2024-14-vault-vulnerable-to-denial-of-service-when-setting-a-proxy-protocol-behavior/68518\",\"source\":\"security@hashicorp.com\"}]}}" } }
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.