StreamparkApplication · Apache
CVE-2022-45802
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 · uneditedStreampark allows any users to upload a jar as application, but there is no mandatory verification of the uploaded file type, causing users to upload some high-risk files, and may upload them to any directory, Users of the affected versions should upgrade to Apache StreamPark 2.0.0 or later
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 confidenceApache StreamPark suffers from an unrestricted file upload vulnerability where the application allows users to upload jar files without validating file types or restricting upload locations. Attackers can upload malicious files to arbitrary directories, potentially achieving remote code execution.
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.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Apache StreamPark versionCheck the version of Apache StreamPark currently deployed in your environment. This is typically visible in the application UI, startup logs, or the pom.xml/build configuration if you have access to the source. Compare the version number against the affected range (all versions prior to 2.0.0).Affected if The installed version is Apache StreamPark any version prior to 2.0.0
-
Locate the file upload functionalityIdentify whether the StreamPark application exposes a file upload feature, specifically for jar files. This is typically found in application sections related to project building, application deployment, or custom JAR management.Affected if The application has an active upload feature for jar or other executable files
-
Examine upload endpoint configurationInspect the web application configuration or the backend code handling file uploads. Look for any file type validation, file extension checking, or content-type validation logic on upload endpoints.Affected if No file type validation, extension validation, or content-type checks are implemented on the upload functionality
-
Check upload directory restrictionsReview the configuration that defines where uploaded files are stored. Determine if the upload mechanism allows writing files to arbitrary directories outside of a designated safe upload location.Affected if Uploaded files can be placed in any directory on the server rather than being restricted to a controlled upload directory
-
Verify jar execution or inclusion pathsIdentify if uploaded jar files are placed in locations where they can be executed by the application or automatically loaded, such as classpaths, bin directories, or locations where the application dynamically loads code.Affected if Uploaded jar files can be executed or dynamically loaded by the application without manual intervention
Your environment is affected if you are running any version of Apache StreamPark prior to 2.0.0 with the jar upload functionality exposed and no file type or directory restrictions on uploads.
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.0.0
Upgrade to Apache StreamPark 2.0.0 or later which implements proper file type validation and directory restrictions for uploads.
Apache StreamPark 2.0.0
- Review the Apache StreamPark 2.0.0 release notes to understand changes and any migration requirements
- Back up your existing Streampark installation including configuration files and data
- Stop the current Streampark service
- Upgrade Streampark to version 2.0.0 or later
- Start the upgraded Streampark service
- Verify that file upload functionality works correctly and that uploaded files are properly validated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Streampark
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45802 — 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-2022-45802 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