{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-5009 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2008-5009 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-5009 is a medium-severity vulnerability in n/a, published on 10 Nov 2008. 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-2008-5009 and fix it if it is affected.\n\nWhat it is: CVE-2008-5009 is a medium-severity vulnerability in n/a, published on 10 Nov 2008. 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-2008-5009 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-2008-5009/ (Markdown: https://insights.sbomify.com/CVE-2008-5009/index.md)","id":"CVE-2008-5009","markdown":"https://insights.sbomify.com/CVE-2008-5009/index.md","name":"CVE-2008-5009","record":{"aliases":["GHSA-3734-5vqh-gp62"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Sun Solstice X.25","requires_auth":"low_privilege","summary":"Local attackers can cause a system panic in Sun Solstice X.25 via a race condition in the s_xout kernel module on multi-CPU systems.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"solstice_x.25","vendor":"sun"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:L/AC:H/Au:N/C:N/I:N/A:C","version":"2.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Race condition in the s_xout kernel module in Sun Solstice X.25 9.2, when running on a multiple CPU machine, allows local users to cause a denial of service (panic) via vectors involving reading the /dev/xty file.","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":"Race condition in n/a","id":"CVE-2008-5009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2008"},"n_packages":0,"n_references":8,"next":{"headline":"Denial of service in n/a","id":"CVE-2008-5010"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2008-5008"},"products":["n/a"],"published":"2008-11-10","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":"Local attackers can cause a system panic in Sun Solstice X.25 via a race condition in the s_xout kernel module on multi-CPU systems.","url":"https://insights.sbomify.com/CVE-2008-5009/"}