Elastic Cloud EnterpriseApplication · Elastic
CVE-2022-23715
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 · uneditedA flaw was discovered in ECE before 3.4.0 that might lead to the disclosure of sensitive information such as user passwords and Elasticsearch keystore settings values in logs such as the audit log or deployment logs in the Logging and Monitoring cluster. The affected APIs are PATCH /api/v1/user and PATCH /deployments/{deployment_id}/elasticsearch/{ref_id}/keystore
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 confidenceIn ECE versions before 3.4.0, the PATCH /api/v1/user and PATCH /deployments/{deployment_id}/elasticsearch/{ref_id}/keystore APIs log sensitive information (user passwords and Elasticsearch keystore values) in plaintext to audit logs and deployment logs, exposing this data to anyone with log access.
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
Elastic Cloud EnterpriseApplication
< 3.4.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed ECE versionRun `ece-version` or check the ECE admin console for the current version numberAffected if Version is before 3.4.0 (e.g., 3.3.x, 3.2.x, etc.)
-
Identify audit log locationLocate the ECE audit log files - typically found in the ECE installer logs directory or via the ECE admin console logging configurationAffected if Audit logs exist and are accessible
-
Search audit logs for plaintext user passwordsGrep or search audit logs for strings matching 'PATCH /api/v1/user' combined with password field values appearing in plaintext (look for password= or "password": patterns in log entries)Affected if Log entries contain the PATCH /api/v1/user API call with plaintext password data
-
Search deployment logs for plaintext keystore valuesGrep or search deployment logs for strings matching 'PATCH /deployments/*/elasticsearch/*/keystore' combined with keystore value data appearing in plaintextAffected if Log entries contain the keystore API call with plaintext sensitive values
-
Check for any historical log exposureReview any archived, backed-up, or exported logs from the time period when ECE versions before 3.4.0 were in useAffected if Archived logs from vulnerable versions contain the sensitive API calls with plaintext data
You are affected if ECE version is before 3.4.0 AND the audit or deployment logs contain plaintext passwords from PATCH /api/v1/user calls or plaintext keystore values from the keystore API calls.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.4.0
Upgrade ECE to version 3.4.0 or later to prevent sensitive data from being written to logs. Additionally, audit existing logs for any exposure of credentials and rotate any compromised passwords or keystore values.
Elastic Cloud Enterprise 3.4.0 or later
- Ensure you have a complete backup of your ECE installation and configuration before starting the upgrade
- Review the official Elastic Cloud Enterprise upgrade documentation for your current version
- Plan a maintenance window as the upgrade will require downtime
- Upgrade Elastic Cloud Enterprise to version 3.4.0 or later
- After upgrade, verify the installation was successful by checking the ECE health endpoints
- Confirm that sensitive information (passwords, keystore values) is no longer being logged by inspecting recent audit logs and deployment logs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Elastic Cloud Enterprise
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23715 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23715 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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