PatchTheCVE63moons vulnerabilities
Recent CVEs affecting 63moons products. 6 tracked.
63moons has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 6. Most recent: 2024-11-04. Highest priority: CVE-2024-51558 (score 51/100).
- CVE-2024-51561 HIGH 7.5 UPGRADE UPGRADE This vulnerability exists in Aero due to improper implementation of OTP validation mechanism in certain API en
- CVE-2024-51560 MEDIUM 4.3 UPGRADE UPGRADE This vulnerability exists in the Wave 2.0 due to improper exception handling for invalid inputs at certain API
- CVE-2024-51559 MEDIUM 6.5 UPGRADE UPGRADE This vulnerability exists in the Wave 2.0 due to improper authorization checks on certain API endpoints
- CVE-2024-51558 CRITICAL 9.8 UPGRADE UPGRADE This vulnerability exists in the Wave 2.0 due to missing restrictions for excessive failed authentication atte
- CVE-2024-51557 MEDIUM 6.5 UPGRADE UPGRADE This vulnerability exists in the Wave 2.0 due to missing rate limiting on OTP requests in an API endpoint
- CVE-2024-51556 MEDIUM 6.5 UPGRADE UPGRADE This vulnerability exists in the Wave 2.0 due to insufficient encryption of sensitive data received at the API
FAQ
How do I fix 63moons 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 63moons being exploited right now?
None of the tracked 63moons CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which 63moons CVE should I patch first?
CVE-2024-51558 currently ranks highest (51/100): This vulnerability exists in the Wave 2.0 due to missing restrictions for excessive failed authentication atte.