Fleet Server
Approved changes feed: RSS · Atom
cpe:2.3:a:elastic:fleet_server:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Elastic (1d0b8d2a-fd47-5b20-b005-34326f9bd037) |
|---|---|
| Product | Fleet Server (1f35da36-c749-5fe2-b802-9b6d31ad7557) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-52975 |
vulnerable | 2026-06-03 14:57:31.061587 |
Fleet Server sensitive information exposure via logs
CRITICAL (9)
An issue was identified in Fleet Server where Fleet policies that could contain sensitive information were logged on INFO and ERROR log levels. The nature of the sensitive information largely depends on the integrations enabled.
Published: 2025-01-23T07:19:39.170Z
Updated: 2025-01-23T14:45:48.260Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-46667 |
vulnerable | 2026-06-03 14:53:10.316245 |
Fleet Server Insertion of Sensitive Information into Log File
HIGH (8.1)
An issue was discovered in Fleet Server >= v8.10.0 and < v8.10.3 where Agent enrolment tokens are being inserted into the Fleet Server’s log file in plain text. These enrolment tokens could allow someone to enrol an agent into an agent policy, and potentially use that to retrieve other secrets in the policy including for Elasticsearch and third-party services. Alternatively a threat actor could potentially enrol agents to the clusters and send arbitrary events to Elasticsearch.
Published: 2023-10-26T00:59:36.713Z
Updated: 2024-09-09T15:53:29.701Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-31421 |
vulnerable | 2026-06-03 14:51:55.727982 |
Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue
MEDIUM (5.9)
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 does not validate the server certificate's IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.
Published: 2023-10-26T03:10:52.684Z
Updated: 2024-08-02T14:53:30.714Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.