Summary
Arbitrary file read using percent-encoded relative paths in FileMiddleware
Workarounds
Upgrade to 4.24.4 or later, or disable FileMiddleware.
References
- Introduced in https://github.com/vapor/vapor/pull/2223
- Fixed by https://github.com/vapor/vapor/pull/2500
For more information
If you have any questions or comments about this advisory:
- Open an issue
- Email us at [email protected]
Impact
Attackers can access data at arbitrary filesystem paths on the same host as an application using FileMiddleware.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2020-15230 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.29.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Version 4.29.4
Frequently Asked Questions
- What is CVE-2020-15230? CVE-2020-15230 is a medium-severity path traversal vulnerability in github.com/vapor/vapor (swift), affecting versions >= 4.0.0-rc.2.5, < 4.29.4. It is fixed in 4.29.4. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2020-15230? CVE-2020-15230 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/vapor/vapor are affected by CVE-2020-15230? github.com/vapor/vapor (swift) versions >= 4.0.0-rc.2.5, < 4.29.4 is affected.
- Is there a fix for CVE-2020-15230? Yes. CVE-2020-15230 is fixed in 4.29.4. Upgrade to this version or later.
- Is CVE-2020-15230 exploitable, and should I be worried? Whether CVE-2020-15230 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2020-15230 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2020-15230? Upgrade
github.com/vapor/vaporto 4.29.4 or later.