{"answers":{"affected":"3 open source packages ship an affected version, including paramiko. It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-0299 in the wild and no public exploit code.","fix":"Upgrade paramiko to a fixed version for your release line: 1.7.1-3 or 1.7.2.","what":"CVE-2008-0299 is a medium-severity vulnerability in n/a, published on 16 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-0299 and fix it if it is affected.\n\nWhat it is: CVE-2008-0299 is a medium-severity vulnerability in n/a, published on 16 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2008-0299 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- paramiko (PyPI): affected all versions; fixed in 1.7.1-3\n- paramiko (PyPI): affected all versions; fixed in 1.7.1-3\n- paramiko (PyPI): affected all versions; fixed in 1.7.2\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-2008-0299/ (Markdown: https://insights.sbomify.com/CVE-2008-0299/index.md)","id":"CVE-2008-0299","markdown":"https://insights.sbomify.com/CVE-2008-0299/index.md","name":"CVE-2008-0299","record":{"aliases":["DEBIAN-CVE-2008-0299","GHSA-wqmm-q65g-2hqr","PYSEC-2008-8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python SSH library","requires_auth":"none","summary":"Attackers can predict RandomPool state in Paramiko to obtain sensitive information from other sessions when using threads or forked processes.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"paramiko","vendor":"python_software_foundation"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by predicting the state of the pool.","ecosystems":["PyPI"],"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":"Paramiko Unsafe randomness usage may allow access to sensitive information","id":"CVE-2008-0299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"weak_cryptography","year":"2008"},"n_packages":3,"n_references":12,"next":{"headline":"Code injection in n/a","id":"CVE-2008-0300"},"packages":[{"ecosystem":"PyPI","fixed":["1.7.1-3"],"introduced":["0"],"last_affected":[],"package":"paramiko","purl":null,"source":"GHSA-wqmm-q65g-2hqr"},{"ecosystem":"PyPI","fixed":["1.7.1-3"],"introduced":["0"],"last_affected":[],"package":"paramiko","purl":"pkg:pypi/paramiko","source":"GHSA-wqmm-q65g-2hqr"},{"ecosystem":"PyPI","fixed":["1.7.2"],"introduced":["0"],"last_affected":[],"package":"paramiko","purl":"pkg:pypi/paramiko","source":"PYSEC-2008-8"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2008-0298"},"products":["n/a"],"published":"2008-01-16","related":[],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can predict RandomPool state in Paramiko to obtain sensitive information from other sessions when using threads or forked processes.","url":"https://insights.sbomify.com/CVE-2008-0299/"}