dbcve.org
MuleApplication · Salesforce

CVE-2021-1627

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-26
Fix available
A fix is available. Upgrade to after 4.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server Side Request Forgery (SSRF) vulnerability in MuleSoft Mule runtime components (versions 3.8.x, 3.9.x, and 4.x released before February 2, 2021). This critical flaw (CVSS 9.8) allows attackers to make the server perform arbitrary requests to internal or external resources, potentially exposing internal services, cloud metadata endpoints, or sensitive internal infrastructure.

MitigationUpgrade Mule runtime to versions released on or after February 2, 2021, or apply vendor-supplied patches. For CloudHub customers, verify that the managed runtime is updated; for on-premise deployments, schedule upgrade of affected runtime instances.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MuleApplication
Affected:>= 3.8.0, <= 4.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Mule runtime installation and version
    Search for Mule installation directories (commonly under /opt/mule, /usr/local/mule, or C:\mule on Windows). Check for version.txt, manifest.mf, or wrapper.conf files in the installation root or lib directory to identify the exact version number.
    Affected if The installed version is 3.8.x, 3.9.x, or any 4.x version up to and including 4.2.2, AND the build date is before February 2, 2021
  2. Identify running Mule processes
    Run 'ps aux | grep mule' on Linux/Unix or check Windows services for 'Mule' or 'MuleSoft' processes. Note the process owner and any associated wrapper or launcher scripts that may reveal version information.
    Affected if A Mule runtime process is running with a version matching the vulnerable range described above
  3. Check Mule deployment descriptors for HTTP connectors
    Inspect Mule configuration files (*.xml files in the apps/ directory or under src/main/app) for <http:listener> or <http:request> connectors. These endpoints that accept URL parameters are the potential attack vectors for SSRF.
    Affected if HTTP listener or request connectors are configured and the underlying Mule runtime version is within the affected range
  4. Verify runtime build date
    Check the Mule runtime build timestamp in manifest files, the mule-release.properties file (often in lib/user or the runtime root), or the wrapper.log for startup timestamps. Compare this date to February 2, 2021.
    Affected if The runtime build date or release date is prior to February 2, 2021 and the version falls within 3.8.0 to 4.2.2

A user is affected if their Mule runtime installation shows a version between 3.8.0 and 4.2.2 (or any 4.x version up to 4.2.2) with a release date before February 2, 2021.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 4.2.2
Interim mitigation

Upgrade Mule runtime to versions released on or after February 2, 2021, or apply vendor-supplied patches. For CloudHub customers, verify that the managed runtime is updated; for on-premise deployments, schedule upgrade of affected runtime instances.

Fix this in Mule Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1627 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data