dbcve.org
KylinApplication · Apache

CVE-2024-48944

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-27
Fix available
A fix is available. Upgrade to 5.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Server-Side Request Forgery (SSRF) vulnerability in Apache Kylin. Through a kylin server, an attacker may forge a request to invoke "/kylin/api/xxx/diag" api on another internal host and possibly get leaked information. There are two preconditions: 1) The attacker has got admin access to a kylin server; 2) Another internal host has the "/kylin/api/xxx/diag" api endpoint open for service. This issue affects Apache Kylin: from 5.0.0 through 5.0.1. Users are recommended to upgrade to version 5.0.2, which fixes the issue.

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

Server-Side Request Forgery (SSRF) in Apache Kylin allows authenticated admin users to forge requests to internal hosts via the '/kylin/api/xxx/diag' endpoint, potentially exposing sensitive internal service information.

MitigationUpgrade to Apache Kylin 5.0.2 or later. Additionally, restrict admin access to trusted users only and implement network segmentation to block internal API endpoints from being accessed via forged requests.

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:>= 5.0.0, < 5.0.2

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
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 checks

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

  1. Identify Apache Kylin installation and version
    Run 'kylin.sh version' or check the Kylin web UI footer for the version number. On command line, you can also look for version info in the installation directory under conf/kylin.properties or in the kylin.war metadata.
    Affected if The installed version is 5.0.0 or 5.0.1 (versions >= 5.0.0 and < 5.0.2 are affected).
  2. Verify admin access is enabled
    Check if admin users exist in the Kylin system by accessing the User Management page in the web UI under 'System' > 'User Management', or query the user table if you have database access.
    Affected if Any enabled admin user account exists in the system (the SSRF flaw requires an authenticated admin user to trigger).
  3. Confirm the diag API endpoint is accessible
    Attempt a HEAD or GET request to an internal endpoint via the diag interface: send a request to 'http://<kylin-host>:<port>/kylin/api/diag/harvest' with an internal hostname (e.g., 127.0.0.1 or an internal IP) as a parameter. Check if the response indicates the server attempted the connection.
    Affected if The API accepts the internal host parameter and attempts to make the request, returning success or failure based on the internal host reachability.
  4. Check network exposure of the Kylin API
    Review firewall rules and Kylin server network configuration to determine if the /kylin/api/* endpoints are reachable from untrusted networks. Look at server.xml in the conf directory for connector bindings.
    Affected if The Kylin web UI and API ports (typically 7070, 8080, or 8443) are exposed to networks beyond localhost or trusted admin workstations.

You are affected if you run Apache Kylin version 5.0.0 or 5.0.1, have admin users configured, and the /kylin/api/*/diag endpoint is network-accessible to those admin users.

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

Upgrade to Apache Kylin 5.0.2 or later. Additionally, restrict admin access to trusted users only and implement network segmentation to block internal API endpoints from being accessed via forged requests.

Recommended fix High confidence

5.0.2

  1. Plan and schedule a maintenance window for the Apache Kylin upgrade
  2. Back up all Kylin configurations, metadata, and existing data
  3. Stop the Kylin service
  4. Upgrade Apache Kylin from the current version (5.0.0 or 5.0.1) to version 5.0.2
  5. Verify the upgrade completed successfully by checking the Kylin version
  6. Restart the Kylin service
  7. Test that the /kylin/api/xxx/diag endpoint no longer allows unauthorized internal network requests

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

Fix this in Kylin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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