{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2009-3278 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-3278 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-3278 is a medium-severity vulnerability in n/a, published on 21 Sep 2009. 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-2009-3278 and fix it if it is affected.\n\nWhat it is: CVE-2009-3278 is a medium-severity vulnerability in n/a, published on 21 Sep 2009. 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-2009-3278 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2009-3278/ (Markdown: https://insights.sbomify.com/CVE-2009-3278/index.md)","id":"CVE-2009-3278","markdown":"https://insights.sbomify.com/CVE-2009-3278/index.md","name":"CVE-2009-3278","record":{"aliases":["GHSA-qx3r-xm4v-rgrh"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"QNAP NAS firmware","requires_auth":"low_privilege","summary":"Weak random number generation in QNAP NAS firmware allows local attackers to brute-force recovery keys, bypassing security controls.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ts-239_pro_firmware","vendor":"qnap"},{"product":"ts-639_pro_firmware","vendor":"qnap"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"The QNAP TS-239 Pro and TS-639 Pro with firmware 2.1.7 0613, 3.1.0 0627, and 3.1.1 0815 use the rand library function to generate a certain recovery key, which makes it easier for local users to determine this key via a brute-force attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2009-3278","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2009"},"n_packages":0,"n_references":4,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2009-3279"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2009-3277"},"products":["n/a"],"published":"2009-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-07","vendors":["n/a"]},"summary":"Weak random number generation in QNAP NAS firmware allows local attackers to brute-force recovery keys, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2009-3278/"}