StreampipesApplication · Apache
CVE-2023-31469
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 · uneditedA REST interface in Apache StreamPipes (versions 0.69.0 to 0.91.0) was not properly restricted to admin-only access. This allowed a non-admin user with valid login credentials to elevate privileges beyond the initially assigned roles. The issue is resolved by upgrading to StreamPipes 0.92.0.
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 StreamPipes versions 0.69.0 to 0.91.0 contain a broken access control vulnerability in the REST interface where admin-only endpoints were not properly restricted. This allowed authenticated non-admin users to perform admin-level operations and elevate privileges beyond their assigned roles.
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
StreampipesApplication
>= 0.69.0, <= 0.91.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Apache StreamPipes versionCheck the version through the administration UI (navigate to About or System Information), inspect the startup logs, or query the API endpoint that returns version information (typically /api/v2/about or similar)Affected if The installed version falls within the range >= 0.69.0 and <= 0.91.0 as shown in the version output
-
Verify REST API endpoints are accessibleConfirm that the REST API interface is enabled and reachable. This can be done by attempting to access the API base URL (commonly http://localhost:8080/streampipes-backend or similar) or checking the configuration file that controls REST API availabilityAffected if The REST API is exposed and accessible to authenticated users, which is the default configuration in affected versions
-
Review user accounts and role assignmentsExamine the user management section of the administration interface or check the users configuration file to identify all non-admin user accounts that have authenticated accessAffected if There are authenticated non-admin users present in the system beyond a single admin-only account
-
Test admin endpoint access from a non-admin accountUsing a non-admin user credentials, attempt to call a known admin-only REST endpoint such as /api/v2/users, /api/v2/roles, /api/v2/admin, or system configuration endpoints. Observe whether the request succeeds or returns a 403 Forbidden responseAffected if Non-admin users can successfully access admin-restricted endpoints and receive HTTP 200 OK responses instead of 403 Forbidden or 401 Unauthorized
The environment is affected if Apache StreamPipes version is between 0.69.0 and 0.91.0 inclusive and the REST API is accessible to non-admin authenticated users who can bypass authorization checks on admin-only endpoints.
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 · scopedUpgrade Apache StreamPipes to version 0.92.0 or later to resolve the improper REST interface access restrictions.
0.92.0
- Stop the running Apache StreamPipes instance
- Backup the existing StreamPipes installation and database
- Upgrade Apache StreamPipes to version 0.92.0 by installing the new release
- Verify the REST interface now properly restricts admin-only access
- Restart the StreamPipes services
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Streampipes
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31469 — 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-31469 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