Elastic Agent vulnerabilities
5 known vulnerabilities affecting elastic/elastic_agent.
Total CVEs
5
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH3MEDIUM2
Vulnerabilities
Page 1 of 1
CVE-2024-52976HIGHCVSS 7.8fixed in 7.17.25≥ 8.0.0, < 8.15.4+2 more2025-05-01
CVE-2024-52976 [HIGH] CWE-829 CVE-2024-52976: Inclusion of functionality from an untrusted control sphere in Elastic Agent subprocess, osqueryd, a
Inclusion of functionality from an untrusted control sphere in Elastic Agent subprocess, osqueryd, allows local attackers to execute arbitrary code via parameter injection.
An attacker requires local access and the ability to modify osqueryd configurations.
cvelistv5nvd
CVE-2023-46669HIGHCVSS 7.1fixed in 8.15.02025-05-01
CVE-2023-46669 [HIGH] CWE-200 CVE-2023-46669: Exposure of sensitive information to local unauthorized actors in Elastic Agent and Elastic Security
Exposure of sensitive information to local unauthorized actors in Elastic Agent and Elastic Security Endpoint can lead to loss of confidentiality and impersonation of Endpoint to the Elastic Stack. This issue was identified by Elastic engineers and Elastic has no indication that it is known or has been exploited by malicious actors.
nvd
CVE-2024-37283MEDIUMCVSS 6.5≥ 8.6.0, < 8.15.02024-08-12
CVE-2024-37283 [MEDIUM] CWE-532 CVE-2024-37283: An issue was discovered whereby Elastic Agent will leak secrets from the agent policy elastic-agent.
An issue was discovered whereby Elastic Agent will leak secrets from the agent policy elastic-agent.yml only when the log level is configured to debug. By default the log level is set to info, where no leak occurs.
cvelistv5nvd
CVE-2023-6687MEDIUMCVSS 6.5≥ 7.0.0, < 7.17.16≥ 8.0.0, < 8.11.3+1 more2023-12-12
CVE-2023-6687 [MEDIUM] CWE-532 CVE-2023-6687: An issue was discovered by Elastic whereby Elastic Agent would log a raw event in its own logs at th
An issue was discovered by Elastic whereby 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 Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private
cvelistv5nvd
CVE-2023-31421HIGHCVSS 7.5≥ 8.0.0, ≤ 8.9.2v8.0.0, 8.9.22023-10-26
CVE-2023-31421 [HIGH] CWE-295 CVE-2023-31421: It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Serve
It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Server did not verify whether the server certificate is valid for the target IP address; however, certificate signature validation is still performed. More specifically, when the client is configured to connect to an IP address (instead of a hostname) it doe
cvelistv5nvd