dbcve.org
StreamparkApplication · Apache

CVE-2025-54981

HIGH · 7.5 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 2.1.7 or later.
See remediation →
84/100
Remediation priority · High
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
Weak Encryption Algorithm in StreamPark, The use of an AES cipher in ECB mode and a weak random number generator for encrypting sensitive data, including JWT tokens, may have risked exposing sensitive authentication data 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.6 use AES encryption in ECB mode, which encrypts identical plaintext blocks into identical ciphertext blocks, revealing encryption patterns. Additionally, a weak random number generator is used for key/IV generation, making the encryption predictable. This exposes JWT authentication tokens and other sensitive data to decryption by attackers who can analyze encryption patterns or predict weak random values.

MitigationUpgrade Apache StreamPark to version 2.1.7 or later, which implements proper AES encryption with secure mode (such as CBC or GCM) and a cryptographically strong random number generator. Prior to production deployment, validate that existing JWT tokens are re-issued with the new encryption scheme.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 StreamPark version
    Check the deployed version by examining the pom.xml file, build artifacts, or application startup logs for the StreamPark version number
    Affected if The installed version is 2.0.0 through 2.1.6 inclusive
  2. Locate encryption configuration
    Search the application configuration files and source code for AES encryption settings, looking specifically for ECB mode configuration or the string 'AES/ECB'
    Affected if ECB mode (AES/ECB) is explicitly configured or used in the encryption implementation
  3. Identify JWT token handling
    Examine the application for JWT token generation, storage, or processing logic, particularly where tokens are encrypted or encoded
    Affected if JWT tokens are processed by the StreamPark application and the encryption uses the vulnerable ECB-based implementation
  4. Check random number generation for keys
    Inspect the key and IV generation code for the presence of non-cryptographic or predictable random number sources (such as java.util.Random instead of java.security.SecureRandom)
    Affected if Weak or predictable random number generation is used for encryption key or IV creation

You are affected if StreamPark version 2.0.0-2.1.6 is running and the application uses its built-in AES encryption for securing sensitive data like JWT tokens with the weak ECB mode implementation.

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 or later, which implements proper AES encryption with secure mode (such as CBC or GCM) and a cryptographically strong random number generator. Prior to production deployment, validate that existing JWT tokens are re-issued with the new encryption scheme.

Recommended fix High confidence

2.1.7

  1. Back up the existing StreamPark installation and all sensitive data including configuration files and database
  2. Stop the currently running StreamPark service
  3. Download Apache StreamPark version 2.1.7 from the official Apache download repository
  4. Install or upgrade to version 2.1.7 following the standard StreamPark upgrade documentation
  5. Start the StreamPark service and verify it is running correctly
  6. Confirm the weak encryption vulnerability is resolved by verifying AES ECB mode is no longer used and the weak random number generator has been replaced

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

Fix this in Streampark 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-54981 — 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-54981 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