StreamparkApplication · Apache
CVE-2023-52290
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 · uneditedIn streampark-console the list pages(e.g: application pages), users can sort page by field. This sort field is sent from the front-end to the back-end, and the SQL query is generated using this field. However, because this sort field isn't validated, there is a risk of SQL injection vulnerability. The attacker must successfully log into the system to launch an attack, which may cause data leakage. Since no data will be written, so this is a low-impact vulnerability. Mitigation: all users should upgrade to 2.1.4, Such parameters will be blocked.
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 confidenceSQL injection vulnerability in StreamPark Console's list page sorting functionality. The sort field parameter submitted from the front-end is directly used in SQL query construction without validation, allowing authenticated attackers to manipulate SQL queries and exfiltrate data from the database.
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
>= 2.0.0, < 2.1.4CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed StreamPark Console versionLocate the StreamPark installation directory and identify the version file or startup logs. Common locations include the project root directory or container metadata. Run: docker ps or check your deployment manifests for the image tag/version.Affected if The installed version is 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.1.0, 2.1.1, 2.1.2, or 2.1.3 (any version >= 2.0.0 and < 2.1.4)
-
Confirm the sorting feature is accessibleLog in to StreamPark Console as an authenticated user. Navigate to any list page that supports sorting (such as the project list, application list, or Flink SQL execution pages). Click on column headers to verify the sorting functionality is operational.Affected if The sorting feature is enabled and functional in the web interface
-
Verify authentication is not enforced for the sorting endpointExamine the API endpoint handling the sort parameter. Check the controller or filter configuration that processes the sort field in list requests. Confirm whether authentication is required for these endpoints.Affected if The sort field parameter can be submitted without additional authorization checks beyond basic authentication
-
Review application logs for suspicious sort parameter valuesSearch StreamPark application logs for unusual patterns in sort parameter usage. Look for SQL syntax fragments, quotes, or UNION statements in sort field values. Query: grep -i 'sort' /path/to/logs/streampark.log | grep -E "'|%|union|select"Affected if Logs contain unexpected SQL fragments or encoded characters in sort parameter values, indicating possible exploitation attempts
The environment is affected if StreamPark Console version is 2.0.0 through 2.1.3 (inclusive) and the list page sorting functionality is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.1.4
Upgrade to StreamPark Console version 2.1.4 or later, which implements parameter blocking for the sort field. If immediate upgrade is not possible, implement server-side validation to whitelist allowed sort field values before constructing SQL queries.
2.1.4
- Backup your existing Streampark installation and database before upgrading
- Download Streampark version 2.1.4 from the official Apache repository
- Stop the current Streampark service
- Upgrade the Streampark installation to version 2.1.4 following standard upgrade procedures
- Start the upgraded Streampark service
- Verify that the application is running correctly and test the sorting functionality to confirm the fix is applied
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
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-52290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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