Use of Hard-coded Credentials in Apache Kylin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2021-45458: 2.15% estimated exploitation activity in the next 30 days; percentile 82.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Apache Kylin provides encryption classes PasswordPlaceholderConfigurer to help users encrypt their passwords. In the encryption algorithm used by this encryption class, the cipher is initialized with a hardcoded key and IV. If users use class PasswordPlaceholderConfigurer to encrypt their password and configure it into kylin's configuration file, there is a risk that the password may be decrypted. This issue affects Apache Kylin 2 version 2.6.6 and prior versions; Apache Kylin 3 version 3.1.2 and prior versions; Apache Kylin 4 version 4.0.0 and prior versions.

Published by the source

8 Jan 2022, 00:43 UTC

Last modified by the source

21 Jul 2023, 19:24 UTC

Source last checked

26 Oct 2026, 16:11 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9fj5-jg6f-qg5r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-45458

Advisory: Use of Hard-coded Credentials in Apache Kylin
IDs: CVE-2021-45458, GHSA-9fj5-jg6f-qg5r
Record: https://patchnext.com/advisories/cve-2021-45458 (revision 1, source checked 26 Oct 2026, 16:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.kylin:kylin 4.0.1, 3.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.kylin:kylin: affected < 3.1.3; >= 4.0.0, <= 4.0.0; fixed in 3.1.3, 4.0.1

## Suggested inspection (read-only)
- Maven org.apache.kylin:kylin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.kylin:kylin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9fj5-jg6f-qg5r (GitHub-reviewed advisory GHSA-9fj5-jg6f-qg5r lists affected ranges: Maven org.apache.kylin:kylin >=0 =4.0.0 <=4.0.0)

Commands are suggestions: review each one before running it.