Elastic Fleet Server
Approved changes feed: RSS · Atom
cpe:2.3:a:elastic:elastic_fleet_server:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Elastic (1d0b8d2a-fd47-5b20-b005-34326f9bd037) |
|---|---|
| Product | Elastic Fleet Server (50efc185-4b47-584a-80e8-1766f93351f9) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/elastic/fleet-server |
purl2cpe | 2026-06-01 10:15:15.484213 |
pkg:golang/github.com/elastic/fleet-server |
purl2cpe | 2026-06-01 10:15:15.484215 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-31421 |
vulnerable | 2026-06-03 14:51:55.730143 |
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.