dbcve.org
Elastic Cloud EnterpriseApplication · Elastic

CVE-2022-23716

MEDIUM · 5.3 CVSS v3.1 Published 2022-09-28
Fix available
A fix is available. Upgrade to 3.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
A flaw was discovered in ECE before 3.1.1 that could lead to the disclosure of the SAML signing private key used for the RBAC features, in deployment logs in the Logging and Monitoring cluster.

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 · moderate confidence

A flaw in Elastic Cloud Enterprise (ECE) before version 3.1.1 causes the SAML signing private key used for Role-Based Access Control (RBAC) to be written to deployment logs within the Logging and Monitoring cluster. This exposes a sensitive cryptographic credential that could allow attackers to forge SAML assertions and gain unauthorized access.

MitigationUpgrade ECE to version 3.1.1 or later to patch the logging vulnerability, and immediately rotate the exposed SAML signing private key to prevent potential authentication bypass.

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
Affected:< 3.1.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Identify ECE version
    Check the installed Elastic Cloud Enterprise version. This is typically available through the ECE admin console, API, or by querying the management cluster. Compare the version number against the affected range (versions before 3.1.1).
    Affected if ECE version is installed and it is lower than 3.1.1
  2. Confirm SAML RBAC is configured
    Verify that Role-Based Access Control (RBAC) is enabled with SAML authentication in the ECE environment. This can be checked through the ECE admin interface under the authentication settings, or by querying the platform configuration for SAML identity provider settings.
    Affected if SAML RBAC is enabled and configured for user authentication
  3. Inspect Logging and Monitoring cluster logs
    Access the Logging and Monitoring cluster that ECE uses for centralized logging. Search deployment logs for patterns matching SAML signing private key material (PEM-encoded private keys, certificate headers, or cryptographic key data that appears in log files).
    Affected if The SAML signing private key material is found in plaintext within the deployment logs of the Logging and Monitoring cluster

A user is affected if their ECE version is below 3.1.1, they have SAML RBAC enabled, and the sensitive SAML signing private key has been inadvertently written to the Logging and Monitoring cluster logs.

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 3.1.1 or later
Fixed in 3.1.1
Interim mitigation

Upgrade ECE to version 3.1.1 or later to patch the logging vulnerability, and immediately rotate the exposed SAML signing private key to prevent potential authentication bypass.

Recommended fix High confidence

Elastic Cloud Enterprise 3.1.1 or later

  1. 1. Review the Elastic Cloud Enterprise upgrade documentation for your current version
  2. 2. Create a complete backup of your ECE installation and configuration
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Upgrade Elastic Cloud Enterprise to version 3.1.1 or later
  5. 5. Verify the upgrade was successful by checking the ECE admin console
  6. 6. Confirm the SAML signing private key is no longer exposed in deployment logs
  7. 7. Rotate the SAML signing private key as a precautionary security measure
Caveat Review Elastic Cloud Enterprise 3.1.1 release notes for any breaking changes between your current version and 3.1.1

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

Fix this in Elastic Cloud Enterprise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23716 — 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-2022-23716 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