yamaguchi vulnerabilities
Recent CVEs affecting yamaguchi products. 1 tracked.
yamaguchi has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2002-12-31. Highest priority: CVE-2002-2023 (score 14/100).
- CVE-2002-2023 LOW 2.1 DOWNGRADE The get_parameter_from_freqency_source function in beep2 1.0, 1.1 and 1.2, when installed setuid root, allows
FAQ
How do I fix yamaguchi vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is yamaguchi being exploited right now?
None of the tracked yamaguchi CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which yamaguchi CVE should I patch first?
CVE-2002-2023 currently ranks highest (14/100): The get_parameter_from_freqency_source function in beep2 1.0, 1.1 and 1.2, when installed setuid root, allows .