{"answers":{"affected":"2 open source packages ship an affected version, including io.ratpack:ratpack-session. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-29480 in the wild and no public exploit code.","fix":"Upgrade io.ratpack:ratpack-session to 1.9.0 or later.","what":"CVE-2021-29480 is a medium-severity vulnerability in ratpack, published on 29 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-29480 and fix it if it is affected.\n\nWhat it is: CVE-2021-29480 is a medium-severity vulnerability in ratpack, published on 29 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-29480 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.ratpack:ratpack-session (Maven): affected all versions; fixed in 1.9.0\n- io.ratpack:ratpack-session (Maven): affected all versions; fixed in 1.9.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-29480/ (Markdown: https://insights.sbomify.com/CVE-2021-29480/index.md)","id":"CVE-2021-29480","markdown":"https://insights.sbomify.com/CVE-2021-29480/index.md","name":"CVE-2021-29480","record":{"aliases":["GHSA-2cc5-23r7-vc4v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ratpack web toolkit","requires_auth":"low_privilege","summary":"Attackers can tamper with session data if they predict the application startup time, as the default signing key is weak and predictable.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ratpack","vendor":"ratpack_project"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"},{"id":"CWE-340","name":"Generation of Predictable Numbers or Identifiers"}],"description":"Ratpack is a toolkit for creating web applications. In versions prior to 1.9.0, the client side session module uses the application startup time as the signing key by default. This means that if an attacker can determine this time, and if encryption is not also used (which is recommended, but is not on by default), the session data could be tampered with by someone with the ability to write cookies. The default configuration is unsuitable for production use as an application restart renders all sessions invalid and is not multi-host compatible, but its use is not actively prevented. As of Ratpack 1.9.0, the default value is a securely randomly generated value, generated at application startup time. As a workaround, supply an alternative signing key, as per the documentation's recommendation.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Default client side session signing key is highly predictable","id":"CVE-2021-29480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Client side sessions should not allow unencrypted storage","id":"CVE-2021-29481"},"packages":[{"ecosystem":"Maven","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"io.ratpack:ratpack-session","purl":null,"source":"GHSA-2cc5-23r7-vc4v"},{"ecosystem":"Maven","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"io.ratpack:ratpack-session","purl":"pkg:maven/io.ratpack/ratpack-session","source":"GHSA-2cc5-23r7-vc4v"}],"prev":{"headline":"Cached redirect poisoning via X-Forwarded-Host header","id":"CVE-2021-29479"},"products":["ratpack"],"published":"2021-06-29","related":[{"cvss_score":9.9,"headline":"Remote Code Execution Vulnerability in Session Storage","id":"CVE-2021-29485","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":7.5,"headline":"io.ratpack:ratpack-core vulnerable to Improper Neutralization of Special Elements in Output ('Injection')","id":"CVE-2019-17513","kev_date_added":null,"published":"2019-10-18"},{"cvss_score":7,"headline":"Cached redirect poisoning via X-Forwarded-Host header","id":"CVE-2021-29479","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":6.5,"headline":"Client side sessions should not allow unencrypted storage","id":"CVE-2021-29481","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":3.7,"headline":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Ratpack","id":"CVE-2019-11808","kev_date_added":null,"published":"2019-05-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["ratpack"]},"summary":"Attackers can tamper with session data if they predict the application startup time, as the default signing key is weak and predictable.","url":"https://insights.sbomify.com/CVE-2021-29480/"}