dbcve.org
CocoonApplication · Apache

CVE-2025-24783

HIGH · 7.5 CVSS v3.1 Published 2025-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
** UNSUPPORTED WHEN ASSIGNED ** Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG) vulnerability in Apache Cocoon. This issue affects Apache Cocoon: all versions. When a continuation is created, it gets a random identifier. Because the random number generator used to generate these identifiers was seeded with the startup time, it may not have been sufficiently unpredictable, and an attacker could use this to guess continuation ids and look up continuations they should not have had access to. As a mitigation, you may enable the "session-bound-continuations" option to make sure continuations are not shared across sessions. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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 confidence

Apache Cocoon's continuation ID generation uses a PRNG seeded with the server startup time, making the random identifiers predictable. An attacker can enumerate or guess continuation IDs to access continuations belonging to other users, achieving unauthorized cross-session access.

MitigationEnable the 'session-bound-continuations' configuration option to tie continuations to specific sessions, preventing cross-session access. Alternatively, restrict network access to trusted users or migrate to a supported framework.

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
CocoonApplication
Affected:all versions

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Apache Cocoon installation
    Check if Apache Cocoon is deployed in your environment by looking for cocoon*.war files in webapp directories, or check running processes for Java applications with Cocoon classpath.
    Affected if Apache Cocoon is found to be running
  2. Locate Cocoon configuration file
    Find the cocoon.xconf or cocoon configuration file in the Cocoon deployment directory or classpath.
    Affected if A Cocoon configuration file exists
  3. Check session-bound-continuations setting
    Search the configuration file for the 'session-bound-continuations' parameter and note its value (enabled/true or disabled/false).
    Affected if The parameter is set to disabled or false
  4. Verify default configuration state
    If the 'session-bound-continuations' parameter is not found in the configuration, check if it defaults to disabled in the default configuration.
    Affected if The setting is absent and defaults to disabled (unprotected)
  5. Confirm continuations are in use
    Verify that Cocoon flow scripts or continuations are actively being used by the application, as the vulnerability only affects applications using this feature.
    Affected if Cocoon continuations are actively used by the application

If Apache Cocoon is running with continuations enabled and the 'session-bound-continuations' option is disabled or not set to true, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable the 'session-bound-continuations' configuration option to tie continuations to specific sessions, preventing cross-session access. Alternatively, restrict network access to trusted users or migrate to a supported framework.

Recommended fix High confidence
  1. This vulnerability affects Apache Cocoon, which is a retired project.
  2. The project maintainers have stated they do not plan to release a version that fixes this issue.
  3. As an alternative, users should migrate to a supported framework or restrict access to the Cocoon instance to trusted users only.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cocoon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24783 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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