Vulnerabilities (CVE)

Filtered by vendor Salesforce Subscribe
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2021-1630 1 Salesforce 1 Mule 2021-08-12 5.0 MEDIUM 7.5 HIGH
XML external entity (XXE) vulnerability affecting certain versions of a Mule runtime component that may affect CloudHub, GovCloud, Runtime Fabric, Pivotal Cloud Foundry, Private Cloud Edition, and on-premise customers.
CVE-2021-1626 1 Salesforce 1 Mule 2021-04-01 7.5 HIGH 9.8 CRITICAL
MuleSoft is aware of a Remote Code Execution vulnerability affecting certain versions of a Mule runtime component that may affect both CloudHub and on-premise customers. Versions affected: Mule 4.1.x and 4.2.x runtime released before February 2, 2021.
CVE-2021-1627 1 Salesforce 1 Mule 2021-04-01 7.5 HIGH 9.8 CRITICAL
MuleSoft is aware of a Server Side Request Forgery vulnerability affecting certain versions of a Mule runtime component that may affect both CloudHub and on-premise customers. This affects: Mule 3.8.x,3.9.x,4.x runtime released before February 2, 2021.
CVE-2021-1628 1 Salesforce 1 Mule 2021-04-01 7.5 HIGH 9.8 CRITICAL
MuleSoft is aware of a XML External Entity (XXE) vulnerability affecting certain versions of a Mule runtime component that may affect both CloudHub and on-premise customers. Affected versions: Mule 4.x runtime released before February 2, 2021.
CVE-2017-15010 1 Salesforce 1 Tough-cookie 2019-06-12 5.0 MEDIUM 7.5 HIGH
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.
CVE-2016-1000232 3 Ibm, Redhat, Salesforce 3 Api Connect, Openshift Container Platform, Tough-cookie 2018-10-31 5.0 MEDIUM 5.3 MEDIUM
NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0.