StreampipesApplication · Apache
CVE-2024-29868
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 · uneditedUse of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Apache StreamPipes user self-registration and password recovery mechanism. This allows an attacker to guess the recovery token in a reasonable time and thereby to take over the attacked user's account. This issue affects Apache StreamPipes: from 0.69.0 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 StreamPipes uses a cryptographically weak PRNG for generating password recovery tokens, allowing attackers to predict tokens and hijack user accounts through the self-registration and password recovery mechanisms.
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.93.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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Apache StreamPipes installationSearch for StreamPipes installation directories, running services, or check common locations such as /opt/streampipes, /home/*/streampipes, or look for the 'streampipes' process via 'ps aux | grep -i stream'Affected if StreamPipes is found installed on the system
-
Determine installed versionCheck the version file or build metadata: look for a version.properties, pom.xml, or the streampipes-core jar manifest. Also check the Docker image tag if running containers. Compare the version against the affected range 0.69.0 to 0.93.0Affected if The installed version falls within >= 0.69.0 and <= 0.93.0
-
Verify self-registration is enabledExamine the StreamPipes configuration file (usually in conf/ or config/ directory) for the setting that controls self-registration, often named 'streampipes.user.registration.enabled' or similar. Check the backend configuration YAML or properties fileAffected if Self-registration is enabled in the configuration
-
Verify password recovery is enabledExamine the same configuration files for password recovery or 'forgot password' functionality settings, typically labeled 'streampipes.password.recovery.enabled' or 'forgot.password.enabled'Affected if Password recovery functionality is enabled
The environment is affected if Apache StreamPipes is installed with a version between 0.69.0 and 0.93.0 and either self-registration or password recovery is enabled.
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 to Apache StreamPipes version 0.95.0 or later which replaces the weak PRNG with a cryptographically secure random number generator.
0.95.0
- Upgrade Apache StreamPipes from any version 0.69.0 through 0.93.0 to version 0.95.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Streampipes
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.0 h
- Testing2.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 $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29868 — 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-29868 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