sweetscape vulnerabilities
Recent CVEs affecting sweetscape products. 5 tracked.
sweetscape has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-07-22. Highest priority: CVE-2019-12553 (score 65/100).
- CVE-2019-12555 HIGH 7.5 DOWNGRADE In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the SubStr
- CVE-2019-12554 HIGH 7.5 DOWNGRADE In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the WSubStr
- CVE-2019-12553 CRITICAL 9.8 DOWNGRADE In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the StrCat
- CVE-2019-12552 MEDIUM 5.5 DOWNGRADE In SweetScape 010 Editor 9.0.1, an integer overflow during the initialization of variables could allow an atta
- CVE-2019-12551 MEDIUM 5.5 DOWNGRADE In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the Memcpy
FAQ
How do I fix sweetscape 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 sweetscape being exploited right now?
None of the tracked sweetscape CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sweetscape CVE should I patch first?
CVE-2019-12553 currently ranks highest (65/100): In SweetScape 010 Editor 9.0.1, improper validation of arguments in the internal implementation of the StrCat .