StreampipesApplication · Apache
CVE-2024-31411
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 · uneditedUnrestricted Upload of File with dangerous type vulnerability in Apache StreamPipes. Such a dangerous type might be an executable file that may lead to a remote code execution (RCE). The unrestricted upload is only possible for authenticated and authorized users. This issue affects Apache StreamPipes: through 0.93.0. Users are recommended to upgrade to version 0.95.0, 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 confidenceApache StreamPices through version 0.93.0 contains an unrestricted file upload vulnerability allowing authenticated and authorized users to upload dangerous file types (e.g., executables) that could result in remote code execution on the underlying system.
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.95.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 by reviewing the Streampipes installation directory, checking the pom.xml file if source is available, or querying the application's About/API endpoint if available. Common locations include the streampipes-version.jar filename or version.properties in the config directory.Affected if The installed version is 0.93.0 or any version prior to 0.95.0
-
Verify if user authentication is enabledCheck the Streampipes configuration files (typically in the conf or config directory) for authentication settings. Look for security-related configurations in application.yml, application.properties, or streampipes-config.yaml.Affected if Authentication is enabled and users can log in, as the vulnerability affects authenticated and authorized users
-
Confirm file upload functionality is accessibleInspect the Streampipes web interface or API documentation to determine if there is a file upload feature available to users. This may include pipeline element uploads, data sink configurations, or custom adapter uploads.Affected if The file upload capability exists and is accessible to authenticated users in the environment
-
Check for unrestricted file type handlingReview the Streampipes configuration or logs to see if there are restrictions on file extensions or MIME types when uploading files. Look for upload whitelist/blacklist configurations.Affected if There are no restrictions or inadequate restrictions on the types of files that can be uploaded (e.g., .exe, .sh, .jar files are permitted)
You are affected if your Streampipes installation is version 0.95.0 or earlier, has user authentication enabled, and includes a file upload feature that permits dangerous file types like executables.
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 · scoped0.95.0
Upgrade Apache StreamPipes to version 0.95.0 or later, which addresses the unrestricted file upload vulnerability.
0.95.0
- Backup the current Apache StreamPipes installation and database
- Stop the StreamPipes service
- Download Apache StreamPipes version 0.95.0 from the official Apache repository
- Install or upgrade to version 0.95.0 following the standard installation instructions
- Verify the upgrade was successful by checking the version number
- Start the StreamPipes service
- Confirm the service is running correctly and the file upload functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Streampipes
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31411 — 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-2024-31411 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