PatchTheCVEmule runtime vulnerabilities and fixes
Recent CVEs affecting mule runtime, with upgrade or downgrade steps. 4 tracked.
Also searched as: muleruntime.
mule runtime has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2020-05-29. Highest priority: CVE-2019-13116 (score 67/100).
- CVE-2020-6937 HIGH 7.5 UPGRADE A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020,
- CVE-2019-15631 CRITICAL 9.8 UPGRADE UPGRADE Remote Code Execution vulnerability in MuleSoft Mule CE/EE 3.x and API Gateway 2.x released before October 31,
- CVE-2019-15630 HIGH 7.5 MITIGATE UPGRADE Directory Traversal in APIkit, HTTP connector, and OAuth2 Provider components in MuleSoft Mule Runtime 3.2.0 a
- CVE-2019-13116 CRITICAL 9.8 UPGRADE The MuleSoft Mule Community Edition runtime engine before 3.8 allows remote attackers to execute arbitrary cod
FAQ
How do I fix mule runtime 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 mule runtime being exploited right now?
None of the tracked mule runtime CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mule runtime CVE should I patch first?
CVE-2019-13116 currently ranks highest (67/100): The MuleSoft Mule Community Edition runtime engine before 3.8 allows remote attackers to execute arbitrary cod.