CVE-2023-46675
Vulnerability from cvelistv5
Published
2023-12-13 07:02
Modified
2024-08-02 20:53
Severity ?
EPSS score ?
Summary
Kibana Insertion of Sensitive Information into Log File
References
▼ | URL | Tags | |
---|---|---|---|
bressers@elastic.co | https://discuss.elastic.co/t/kibana-8-11-2-7-17-16-security-update-esa-2023-27/349182/2 | Mailing List, Vendor Advisory |
{ "containers": { "adp": [ { "providerMetadata": { "dateUpdated": "2024-08-02T20:53:20.893Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "x_transferred" ], "url": "https://discuss.elastic.co/t/kibana-8-11-2-7-17-16-security-update-esa-2023-27/349182/2" } ], "title": "CVE Program Container" } ], "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Kibana", "vendor": "Elastic", "versions": [ { "lessThan": "7.17.16", "status": "affected", "version": "7.13.0", "versionType": "semver" }, { "lessThan": "8.11.2", "status": "affected", "version": "8.0.0", "versionType": "semver" } ] } ], "datePublic": "2023-12-12T17:00:00.000Z", "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eAn\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eissue\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error or in the event where debug level logging is enabled in \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eKibana\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e. \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eElastic\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e has released Kibana 8.11.2 which resolves this issue. The messages recorded in the log may contain Account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users, Elastic Security package policy objects which can contain private keys, bearer token, and sessions of 3rd-party integrations and finally Authorization headers, client \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003esecrets\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e, local file paths, and stack traces. The issue may occur in any Kibana instance running an affected version that could potentially receive an unexpected error when \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003ecommunicating\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e to Elasticsearch causing it to include \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003esensitive\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003edata\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003einto\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e Kibana error logs. It could also occur under specific circumstances when debug level logging is enabled in Kibana. \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eNote\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e: \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eIt\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003ewas\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003efound\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003ethat\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003ethe\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003efix\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e for \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eESA\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e-\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e2023\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e-25 in Kibana \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e8\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e.11.1 for \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003ea\u003c/span\u003e \u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003esimilar\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e issue was \u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003eincomplete\u003c/span\u003e\u003cspan style=\"background-color: rgba(70, 149, 74, 0.15);\"\u003e.\u003c/span\u003e\u003cbr\u003e" } ], "value": "An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error or in the event where debug level logging is enabled in Kibana. Elastic has released Kibana 8.11.2 which resolves this issue. The messages recorded in the log may contain Account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users, Elastic Security package policy objects which can contain private keys, bearer token, and sessions of 3rd-party integrations and finally Authorization headers, client secrets, local file paths, and stack traces. The issue may occur in any Kibana instance running an affected version that could potentially receive an unexpected error when communicating to Elasticsearch causing it to include sensitive data into Kibana error logs. It could also occur under specific circumstances when debug level logging is enabled in Kibana. Note: It was found that the fix for ESA-2023-25 in Kibana 8.11.1 for a similar issue was incomplete.\n" } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "HIGH", "attackVector": "ADJACENT_NETWORK", "availabilityImpact": "HIGH", "baseScore": 8, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H", "version": "3.1" }, "format": "CVSS", "scenarios": [ { "lang": "en", "value": "GENERAL" } ] } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-532", "description": "CWE-532 Insertion of Sensitive Information into Log File", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2023-12-13T07:02:07.706Z", "orgId": "271b6943-45a9-4f3a-ab4e-976f3fa05b5a", "shortName": "elastic" }, "references": [ { "url": "https://discuss.elastic.co/t/kibana-8-11-2-7-17-16-security-update-esa-2023-27/349182/2" } ], "source": { "discovery": "UNKNOWN" }, "title": "Kibana Insertion of Sensitive Information into Log File", "x_generator": { "engine": "Vulnogram 0.1.0-dev" } } }, "cveMetadata": { "assignerOrgId": "271b6943-45a9-4f3a-ab4e-976f3fa05b5a", "assignerShortName": "elastic", "cveId": "CVE-2023-46675", "datePublished": "2023-12-13T07:02:07.706Z", "dateReserved": "2023-10-24T17:28:32.186Z", "dateUpdated": "2024-08-02T20:53:20.893Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2023-46675\",\"sourceIdentifier\":\"bressers@elastic.co\",\"published\":\"2023-12-13T07:15:23.077\",\"lastModified\":\"2023-12-18T17:59:39.613\",\"vulnStatus\":\"Analyzed\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error or in the event where debug level logging is enabled in Kibana. Elastic has released Kibana 8.11.2 which resolves this issue. The messages recorded in the log may contain Account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users, Elastic Security package policy objects which can contain private keys, bearer token, and sessions of 3rd-party integrations and finally Authorization headers, client secrets, local file paths, and stack traces. The issue may occur in any Kibana instance running an affected version that could potentially receive an unexpected error when communicating to Elasticsearch causing it to include sensitive data into Kibana error logs. It could also occur under specific circumstances when debug level logging is enabled in Kibana. Note: It was found that the fix for ESA-2023-25 in Kibana 8.11.1 for a similar issue was incomplete.\\n\"},{\"lang\":\"es\",\"value\":\"Elastic descubri\u00f3 un problema por el cual se puede registrar informaci\u00f3n confidencial en los registros de Kibana en caso de un error o en el caso de que el registro de nivel de depuraci\u00f3n est\u00e9 habilitado en Kibana. Elastic lanz\u00f3 Kibana 8.11.2 que resuelve este problema. Los mensajes registrados en el registro pueden contener credenciales de cuenta para el usuario kibana_system, claves API y credenciales de los usuarios finales de Kibana, objetos de pol\u00edtica del paquete Elastic Security que pueden contener claves privadas, tokens de portador y sesiones de integraciones de terceros y, finalmente, autorizaci\u00f3n de encabezados, secretos de cliente, rutas de archivos locales y seguimientos de pila. El problema puede ocurrir en cualquier instancia de Kibana que ejecute una versi\u00f3n afectada y que potencialmente podr\u00eda recibir un error inesperado al comunicarse con Elasticsearch, lo que provocar\u00eda que se incluyeran datos confidenciales en los registros de errores de Kibana. Tambi\u00e9n podr\u00eda ocurrir en circunstancias espec\u00edficas cuando el registro de nivel de depuraci\u00f3n est\u00e1 habilitado en Kibana. Nota: Se descubri\u00f3 que la soluci\u00f3n para ESA-2023-25 en Kibana 8.11.1 para un problema similar estaba incompleta.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\"},\"exploitabilityScore\":2.8,\"impactScore\":3.6},{\"source\":\"bressers@elastic.co\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H\",\"attackVector\":\"ADJACENT_NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\",\"baseScore\":8.0,\"baseSeverity\":\"HIGH\"},\"exploitabilityScore\":1.3,\"impactScore\":6.0}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-532\"}]},{\"source\":\"bressers@elastic.co\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-532\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"7.13.0\",\"versionEndExcluding\":\"7.17.16\",\"matchCriteriaId\":\"E2637EAD-4E01-41A7-B156-65490431F21E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"8.0.0\",\"versionEndExcluding\":\"8.11.2\",\"matchCriteriaId\":\"CABAA148-5196-401E-A56F-874D12A3E8B7\"}]}]}],\"references\":[{\"url\":\"https://discuss.elastic.co/t/kibana-8-11-2-7-17-16-security-update-esa-2023-27/349182/2\",\"source\":\"bressers@elastic.co\",\"tags\":[\"Mailing List\",\"Vendor Advisory\"]}]}}" } }
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.