dbcve.org
Fleet ServerApplication · Elastic

CVE-2023-46667

HIGH · 8.1 CVSS v3.1 Published 2023-10-26
Fix available
A fix is available. Upgrade to 8.10.3 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Agent enrollment tokens are being written in plain text to Fleet Server log files starting in v8.10.0. An attacker with log file access can retrieve these tokens and use them to enroll agents into agent policies, potentially exposing stored secrets for Elasticsearch and third-party integrations, or injecting arbitrary events into Elasticsearch.

MitigationUpgrade Fleet Server to v8.10.3 or later to receive the fix. Additionally, rotate any enrollment tokens that may have been exposed in logs since v8.10.0 as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fleet ServerApplication
Affected:>= 8.10.0, < 8.10.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Fleet Server version
    Query your Fleet Server installation for its version number (e.g., using fleetctl or through the Fleet UI/API)
    Affected if The installed version is 8.10.0, 8.10.1, or 8.10.2 (i.e., >= 8.10.0 and < 8.10.3)
  2. Locate Fleet Server log files
    Identify where Fleet Server logs are written in your environment (default locations or custom paths as configured)
    Affected if Fleet Server logs exist and the server version is in the affected range
  3. Search logs for enrollment token patterns
    Inspect Fleet Server log files for occurrences of enrollment tokens - look for strings matching enrollment token formats or API keys that may have been logged during agent enrollment operations
    Affected if Plain text enrollment tokens or API keys are found in the logs
  4. Review agent enrollment activity
    Check Fleet audit logs or agent enrollment records for any unauthorized or unexpected agent enrollments that occurred during the affected version timeframe
    Affected if New agents were enrolled that you did not initiate or recognize

You are affected if Fleet Server version is 8.10.0 through 8.10.2 AND plain text enrollment tokens are present in logs or unauthorized enrollments occurred.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.10.3 or later
Fixed in 8.10.3
Interim mitigation

Upgrade Fleet Server to v8.10.3 or later to receive the fix. Additionally, rotate any enrollment tokens that may have been exposed in logs since v8.10.0 as a precautionary measure.

Recommended fix High confidence

Fleet Server 8.10.3 or later

  1. 1. Identify the current Fleet Server version in use (e.g., via 'fleetctl version' or Kibana > Fleet > Settings)
  2. 2. Confirm the installed version is >= 8.10.0 and < 8.10.3 to determine if the system is vulnerable
  3. 3. Review the Elastic upgrade documentation for Fleet Server at https://www.elastic.co/guide/en/fleet/current/upgrade-fleet.html
  4. 4. Create a backup of current Fleet Server configuration, policies, and enrolment tokens
  5. 5. Perform a test upgrade in a staging environment to verify compatibility
  6. 6. During a scheduled maintenance window, upgrade Fleet Server to version 8.10.3 or later
  7. 7. After upgrade, verify the fix by checking that enrolment tokens are no longer written to log files (inspect recent Fleet Server logs)
  8. 8. Regenerate any enrolment tokens that may have been exposed in logs prior to the upgrade
Caveat Standard Elastic upgrade precautions apply - review release notes for any breaking changes between 8.10.x versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fleet Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46667 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data