Safeguard
Vulnerability Analysis•

CVE-2023-29055: High Credential Exposure in Apache Kylin Config Page

CVE-2023-29055 exposes kylin.properties, possibly with credentials, over plain HTTP in Apache Kylin 2.0.0 to 4.0.3. Upgrade to 4.0.4 and turn on HTTPS.

Safeguard Security Team
3 min read

CVE-2023-29055 affects Apache Kylin 2.0.0 to 4.0.3. The Server Config web interface shows kylin.properties, which may hold credentials, and over plain HTTP a network sniffer can read it. NVD scores it 7.5, High. Upgrade to 4.0.4, which filters sensitive content, and turn on HTTPS.

What's affected

  • Apache Kylin 2.0.0 through 4.0.3: affected, per the NVD record and the Apache announcement.
  • Apache Kylin 4.0.4: fixed. It filters the sensitive content shown in the Server Config interface.

The issue applies when the service runs over HTTP or another plain text protocol. I found no second severity score. NVD gives 7.5, High, and the Apache text does not give its own.

How to check if you're exposed

Find the Kylin version in the web interface or your install directory, and check whether the service is reachable over plain HTTP. From a machine on the same network, a request to the Kylin port using the http scheme that succeeds without redirecting means the content is not encrypted.

Then review kylin.properties on the server. Look for passwords, keys or tokens stored in plain text, and for any that you should treat as exposed if the service has run over HTTP on a shared network.

What to do now

  1. Upgrade to Apache Kylin 4.0.4 or later.
  2. Turn on HTTPS so that network traffic is encrypted, as the Apache announcement recommends.
  3. Avoid putting credentials in kylin.properties, or at least not in plain text.
  4. Use network firewalls so the server side is not reachable by external attackers.
  5. Rotate any credential that was stored in kylin.properties if the service ran over HTTP on a network you do not fully control.

Why it matters

The record classes the flaw as CWE-522 (Insufficiently Protected Credentials). Two things combine here. The configuration page displays a file that can hold secrets, and the service may send it unencrypted. Either alone is manageable. Together, anyone who can watch the network path can read the credentials without logging in.

The Apache announcement lists four steps, and they work as a layered answer. Encrypt the traffic, keep secrets out of the file, limit network reach, and upgrade so the page filters sensitive values. If you do only the upgrade, the transport problem remains for other data.

Rotation matters as much as patching. Credentials that have crossed a plain network may already be seen, and a patched page does not undo that. Treat the upgrade as the end of exposure going forward, and rotation as the clean-up for the past.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does HTTPS alone fix this?

It protects the content in transit, which is the route the record describes. The Apache announcement still recommends upgrading to 4.0.4 and keeping credentials out of plain text.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.