dbcve.org
KylinApplication · Apache

CVE-2023-29055

HIGH · 7.5 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 4.0.4 or later.
See remediation →
84/100
Remediation priority · High
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
In Apache Kylin version 2.0.0 to 4.0.3, there is a Server Config web interface that displays the content of file 'kylin.properties', that may contain serverside credentials. When the kylin service runs over HTTP (or other plain text protocol), it is possible for network sniffers to hijack the HTTP payload and get access to the content of kylin.properties and potentially the containing credentials. To avoid this threat, users are recommended to  * Always turn on HTTPS so that network payload is encrypted. * Avoid putting credentials in kylin.properties, or at least not in plain text. * Use network firewalls to protect the serverside such that it is not accessible to external attackers. * Upgrade to version Apache Kylin 4.0.4, which filters out the sensitive content that goes to the Server Config web interface.

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

Apache Kylin's Server Config web interface exposes the contents of the kylin.properties file, which may contain plain-text server-side credentials. When the service runs over unencrypted HTTP, network sniffers can intercept the HTTP traffic and gain access to these sensitive credentials.

MitigationEnable HTTPS to encrypt network traffic, avoid storing credentials in plain text in kylin.properties, and upgrade to Apache Kylin 4.0.4 which filters sensitive content from the Server Config interface.

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
KylinApplication
Affected:>= 2.0.0, < 4.0.4

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
High
Integrity
None
Availability
None

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

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

  1. Identify Apache Kylin installation and version
    Locate the kylin.properties file (commonly in $KYLIN_HOME/conf/ or /kylin/conf/) and check its version.properties or run 'kylin --version' if available. Alternatively, check the kylin.properties for version indicators or look for version info in the Kylin web UI footer.
    Affected if Version is >= 2.0.0 and < 4.0.4
  2. Verify if service runs over HTTP
    Check the server configuration for the web UI binding. Look for 'kylin.server.bind.host' and 'kylin.server.bind.port' in kylin.properties. Check if HTTPS is configured by searching for 'kylin.server.ssl' settings or examine the URL used to access the Server Config interface - it should start with 'https://' for encrypted traffic.
    Affected if The Server Config UI is accessible over http:// (not https://)
  3. Locate kylin.properties file
    Find kylin.properties in the Kylin conf directory (commonly $KYLIN_HOME/conf/kylin.properties or /kylin/conf/kylin.properties). This file contains the configuration loaded by the Kylin server.
    Affected if kylin.properties exists and is readable by the service account
  4. Check for sensitive credentials in kylin.properties
    Open kylin.properties and search for patterns that indicate credentials: look for properties containing 'password', 'secret', 'key', 'token', 'credential' in the property name, and examine their values. Common sensitive properties include kylin.storage.columnar.predcanKey, datasource passwords, or admin credentials.
    Affected if kylin.properties contains any property with a plain-text value that looks like a password, secret, key, or token

You are affected if you run Apache Kylin version 2.0.0 to 4.0.3, access the Server Config interface over HTTP, and your kylin.properties file contains plain-text sensitive credentials.

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

Enable HTTPS to encrypt network traffic, avoid storing credentials in plain text in kylin.properties, and upgrade to Apache Kylin 4.0.4 which filters sensitive content from the Server Config interface.

Recommended fix High confidence

Apache Kylin 4.0.4

  1. Upgrade Apache Kylin to version 4.0.4 or later
  2. Configure the Kylin service to run over HTTPS instead of HTTP
  3. Ensure network traffic is encrypted to prevent credential sniffing
  4. Consider migrating sensitive credentials from plain-text kylin.properties to a secure credential storage mechanism

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

Fix this in Kylin 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-2023-29055 — 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-29055 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