StreamparkApplication · Apache
CVE-2022-46365
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 · uneditedApache StreamPark 1.0.0 before 2.0.0 When the user successfully logs in, to modify his profile, the username will be passed to the server-layer as a parameter, but not verified whether the user name is the currently logged user and whether the user is legal, This will allow malicious attackers to send any username to modify and reset the account, 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 confidenceThis is an Insecure Direct Object Reference (IDOR) / Broken Access Control vulnerability in Apache StreamPark 1.0.0 before 2.0.0. The profile modification endpoint accepts a username parameter from the client without server-side verification that the requesting user is authorized to modify that specific profile. An authenticated attacker can modify or reset any user's account by simply specifying a different username in the profile update request.
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
>= 1.0.0, < 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Apache StreamPark installation versionLocate the version file or check the build metadata in the StreamPark installation directory. Common paths include version files in the conf/ directory, or check the pom.xml if source is available. Alternatively, query the API endpoint /api/version or check startup logs for version information.Affected if The installed version is 1.0.0 or any version greater than 1.0.0 but less than 2.0.0
-
Verify the profile modification endpoint existsIdentify if the profile update API endpoint is accessible. This typically involves checking for endpoints under /api/user or /api/profile that handle user profile modifications. Review API routing configuration or proxy settings.Affected if The profile modification endpoint is exposed and accessible to authenticated users
-
Test for missing server-side username validationUsing an authenticated session, send a profile update request (typically POST or PUT to the profile endpoint) with a username parameter different from the authenticated user's username. Observe whether the server accepts and processes the request without rejecting it based on username mismatch.Affected if The server allows modifying a different user's profile by specifying an arbitrary username parameter in the request
A user is affected if they are running Apache StreamPark version 1.0.0 through any version before 2.0.0 and the profile modification endpoint accepts a username parameter that differs from the authenticated user's identity.
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 server-side validation to ensure the authenticated user can only modify their own profile.
Apache StreamPark 2.0.0 or later
- Download Apache StreamPark 2.0.0 or later from the official Apache distribution repository
- Review the upgrade guide documentation for migration steps from 1.x to 2.x
- Backup the existing configuration and database data
- Stop the currently running StreamPark 1.x instance
- Install StreamPark 2.0.0 or later
- Restore or migrate configuration files as needed
- Start the StreamPark 2.0.0 or later instance
- Verify that the profile modification vulnerability is fixed by attempting to modify another user's profile (should fail)
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 / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46365 — 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-46365 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