dbcve.org
StreamparkApplication · Apache

CVE-2025-54947

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 2.1.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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 StreamPark versions 2.0.0 through 2.1.7, a security vulnerability involving a hard-coded encryption key exists. This vulnerability occurs because the system uses a fixed, immutable key for encryption instead of dynamically generating or securely configuring the key. Attackers may obtain this key through reverse engineering or code analysis, potentially decrypting sensitive data or forging encrypted information, leading to information disclosure or unauthorized system access. This issue affects Apache StreamPark: from 2.0.0 before 2.1.7. Users are recommended to upgrade to version 2.1.7, 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

Apache StreamPark versions 2.0.0 through 2.1.7 contain a hard-coded encryption key used for securing sensitive data. Attackers can extract this static key through reverse engineering or code analysis, then decrypt previously encrypted data or forge encrypted payloads to gain unauthorized system access.

MitigationUpgrade Apache StreamPark to version 2.1.7 which removes the hard-coded key and implements proper key management. Additionally, rotate any sensitive data that may have been encrypted with the compromised key.

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
StreamparkApplication
Affected:>= 2.0.0, < 2.1.7

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

CVSS:3.1/AV:N/AC:L/PR:N/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 StreamPark version
    Check the installed Apache StreamPark version by reviewing the application manifest, pom.xml, or running 'streampark --version' if available. Also check the build artifacts or Docker image tags if running in containers.
    Affected if The installed version is 2.0.0 through 2.1.7 inclusive
  2. Locate encryption-related configuration files
    Search for configuration files in the StreamPark deployment directory that contain encryption settings, password storage, or secret management. Look for files like application.yml, application.properties, or custom config files in the conf/ or config/ directories.
    Affected if Configuration files contain hard-coded encryption keys, static secrets, or embedded password encryptors
  3. Inspect source code or JAR artifacts for hard-coded keys
    If access to source code or compiled JAR/WAR files is available, search for hard-coded strings matching patterns like 'encrypt', 'cipher', 'secret', 'key', or 'password' in cryptographic utility classes. Decompile JAR files if necessary to inspect compiled code.
    Affected if Source code or decompiled classes contain hard-coded encryption keys or static secrets used for data encryption
  4. Check for encrypted sensitive data
    Review stored data in databases, configuration files, or credential stores that may contain encrypted values. Identify any encrypted passwords, tokens, API keys, or other sensitive fields.
    Affected if Encrypted sensitive data exists that was protected using the hard-coded key from the affected version range

If the deployed StreamPark version falls within 2.0.0 to 2.1.7, or if hard-coded encryption keys are found in the codebase or configuration, the environment is affected by this vulnerability.

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

Upgrade Apache StreamPark to version 2.1.7 which removes the hard-coded key and implements proper key management. Additionally, rotate any sensitive data that may have been encrypted with the compromised key.

Recommended fix High confidence

2.1.7

  1. 1. Back up your current Apache StreamPark installation, configuration files, and any persisted data.
  2. 2. Download Apache StreamPark version 2.1.7 from the official Apache download page (https://streampark.apache.org/download).
  3. 3. Review the official upgrade guide at https://streampark.apache.org/docs/upgrade for migration instructions between your current version and 2.1.7.
  4. 4. Stop the currently running StreamPark services.
  5. 5. Install or deploy version 2.1.7 following the standard installation process.
  6. 6. Restore your backed-up configurations, adapting them as needed for any new configuration parameters in 2.1.7.
  7. 7. Start the StreamPark 2.1.7 services.
  8. 8. Verify that the application functions correctly and that the hard-coded encryption key vulnerability is resolved.
Caveat Review release notes for 2.1.7 to identify any configuration or API changes that may require adjustments during upgrade

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

Fix this in Streampark Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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