# CVE-2019-15630: Mule modules contain Directory Traversal

> Remote attackers can read arbitrary files accessible to the Mule process via directory traversal in APIkit, HTTP connector, and OAuth2 components.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mwh9-gr45-xvv4

## What is CVE-2019-15630?

CVE-2019-15630 is a high-severity path traversal vulnerability in Salesforce, Inc. Mulesoft, published on 30 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory Traversal in APIkit, HTTP connector, and OAuth2 Provider components in MuleSoft Mule Runtime 3.2.0 and higher released before August 1 2019, MuleSoft Mule Runtime 4.1.0 and higher released before August 1 2019, and all versions of MuleSoft API Gateway released before August 1 2019 allow remote attackers to read files accessible to the Mule process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-15630?

2 open source packages ship an affected version, including org.mule.runtime:mule. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.mule.runtime:mule` | Maven | From 3.0.0 to 4.1.5 | None |
| `org.mule.runtime:mule` | Maven | From 3.0.0 to 4.1.5 | None |

Products: Mulesoft Api Gateway, Mulesoft Mule Runtime.

## How do I fix CVE-2019-15630?

No fix has been published for CVE-2019-15630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-15630 being exploited?

There is no known exploitation of CVE-2019-15630 in the wild and no public exploit code.

## Other vulnerabilities in Salesforce, Inc. Mulesoft

- [CVE-2019-15631](https://insights.sbomify.com/CVE-2019-15631/): Code injection in Mule API Gateway 2.x (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15630 and fix it if it is affected.

What it is: CVE-2019-15630 is a high-severity path traversal vulnerability in Salesforce, Inc. Mulesoft, published on 30 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15630 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.mule.runtime:mule (Maven): affected from 3.0.0 up to 4.1.5; no fix listed
- org.mule.runtime:mule (Maven): affected from 3.0.0 up to 4.1.5; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-15630/ (Markdown: https://insights.sbomify.com/CVE-2019-15630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-15630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-15630
- OSV: https://osv.dev/vulnerability/CVE-2019-15630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-15630/
Summaries are generated and may contain mistakes; the official description above is the record.