# CVE-2025-24783: Apache Cocoon: continuations may not be private > Attackers can guess continuation IDs due to weak PRNG seeding, accessing unauthorized data in the retired Apache Cocoon framework. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 27 Jan 2025 - **Updated:** 28 Jan 2025 - **Also known as:** GHSA-pff9-53m5-qr56 ## What is CVE-2025-24783? CVE-2025-24783 is a high-severity vulnerability in Apache Cocoon, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ** 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. Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)) ## Which versions are affected by CVE-2025-24783? 4 open source packages ship an affected version, including org.apache.cocoon:cocoon-forms-impl and org.apache.cocoon:cocoon-sitemap-impl. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.cocoon:cocoon-forms-impl` | Maven | All versions to 2.3.0 | None | | `org.apache.cocoon:cocoon-forms-impl` | Maven | All versions to 2.3.0 | None | | `org.apache.cocoon:cocoon-sitemap-impl` | Maven | All versions to 2.3.0 | None | | `org.apache.cocoon:cocoon-sitemap-impl` | Maven | All versions to 2.3.0 | None | Products: Apache Cocoon. ## How do I fix CVE-2025-24783? No fix has been published for CVE-2025-24783 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-24783 being exploited? There is no known exploitation of CVE-2025-24783 in the wild and no public exploit code. ## Other vulnerabilities in Apache Cocoon - [CVE-2022-45135](https://insights.sbomify.com/CVE-2022-45135/): Apache Cocoon: SQL injection in DatabaseCookieAuthenticatorAction (critical 9.8) - [CVE-2023-49733](https://insights.sbomify.com/CVE-2023-49733/): Apache Cocoon's StreamGenerator is vulnerable to XXE injection (critical 9.8) - [CVE-2020-11991](https://insights.sbomify.com/CVE-2020-11991/): XML external entity in Apache Cocoon (high 7.5) - [CVE-2003-1172](https://insights.sbomify.com/CVE-2003-1172/): Path traversal in n/a (medium 5.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-24783 and fix it if it is affected. What it is: CVE-2025-24783 is a high-severity vulnerability in Apache Cocoon, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-24783 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.cocoon:cocoon-forms-impl (Maven): affected all versions up to 2.3.0; no fix listed - org.apache.cocoon:cocoon-forms-impl (Maven): affected all versions up to 2.3.0; no fix listed - org.apache.cocoon:cocoon-sitemap-impl (Maven): affected all versions up to 2.3.0; no fix listed - org.apache.cocoon:cocoon-sitemap-impl (Maven): affected all versions up to 2.3.0; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-24783/ (Markdown: https://insights.sbomify.com/CVE-2025-24783/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24783 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24783 - OSV: https://osv.dev/vulnerability/CVE-2025-24783 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-24783/ Summaries are generated and may contain mistakes; the official description above is the record.