dbcve.org
KylinApplication · Apache

CVE-2025-30067

HIGH · 7.2 CVSS v3.1 Published 2025-03-27
Fix available
A fix is available. Upgrade to 5.0.2 or later.
See remediation →
78/100
Remediation priority · High
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
Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Kylin. If an attacker gets access to Kylin's system or project admin permission, the JDBC connection configuration maybe altered to execute arbitrary code from the remote. You are fine as long as the Kylin's system and project admin access is well protected. This issue affects Apache Kylin: from 4.0.0 through 5.0.1. Users are recommended to upgrade to version 5.0.2 or above, 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

Code injection vulnerability in Apache Kylin allows attackers with system or project admin permissions to modify JDBC connection configurations to execute arbitrary remote code due to improper control of code generation. The vulnerability exists in versions 4.0.0 through 5.0.1.

MitigationUpgrade to Apache Kylin 5.0.2 or above. As a compensating control, strictly protect system and project admin access to prevent unauthorized configuration changes.

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:>= 4.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 version
    Check the Kylin installation version through the web UI under 'System' > 'About' or by inspecting the kylin.properties or kylin-version.conf file in the Kylin home directory
    Affected if The installed version is 4.0.0 through 5.0.1 (versions less than 5.0.2)
  2. Verify admin role assignments
    Review user role assignments in Kylin's user management section under 'System' > 'Users' or 'System' > 'Roles' to identify accounts with 'SYSTEM_ADMIN' or 'PROJECT_ADMIN' privileges
    Affected if Any untrusted or compromised account holds system admin or project admin permissions
  3. Inspect JDBC connection configuration access
    Navigate to 'System' > 'Data Source' > 'JDBC' or 'Project' > 'Settings' > 'Data Source' to confirm the JDBC connection configuration interface is accessible
    Affected if The JDBC configuration panel is reachable by admin users without additional access controls
  4. Check for unauthorized JDBC connection strings
    Review existing JDBC data source configurations for suspicious or unexpected connection strings, particularly those containing code execution patterns
    Affected if JDBC connection strings contain potentially malicious connection parameters or point to untrusted remote sources

You are affected if your Kylin version is between 4.0.0 and 5.0.1 AND any user with admin permissions can modify JDBC connection configurations.

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 above. As a compensating control, strictly protect system and project admin access to prevent unauthorized configuration changes.

Recommended fix High confidence

5.0.2 or later

  1. 1. Back up all Kylin configurations, metadata, and data directories before proceeding
  2. 2. Stop the Kylin service to prevent active connections during upgrade
  3. 3. Download Apache Kylin version 5.0.2 or later from the official Apache Kylin releases
  4. 4. Install or extract the new Kylin 5.0.2+ version to replace the existing installation
  5. 5. Migrate configurations from the old installation to the new version, carefully reviewing JDBC connection settings
  6. 6. Start the Kylin service and verify it runs without errors
  7. 7. Validate that the upgrade was successful by logging into Kylin and checking system health
  8. 8. Review user access controls and ensure system/project admin permissions are properly secured
Caveat Review release notes for migration notes between 4.x/5.0.x to 5.0.2, as configuration changes may be required

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

Fix this in Kylin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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