Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-3224 | An issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default. |
Github GHSA |
GHSA-hj4r-2c9c-29h3 | Elastic Beats inserts sensitive information into log file |
Mon, 02 Dec 2024 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Status: PUBLISHED
Assigner: elastic
Published:
Updated: 2024-12-02T14:30:39.538Z
Reserved: 2023-12-02T16:06:57.310Z
Link: CVE-2023-49922
Updated: 2024-08-02T22:09:49.280Z
Status : Modified
Published: 2023-12-12T19:15:08.307
Modified: 2024-11-21T08:34:00.663
Link: CVE-2023-49922
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA