# CVE-2020-5398: RFD Attack via "Content-Disposition" Header Sourced from Request Input by Spring MVC or Spring WebFlux Application > Attackers can trigger reflected file downloads via unsanitized Content-Disposition headers, potentially leading to code execution or security bypasses in Spring applications. - **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 16 Jan 2020 - **Updated:** 8 Oct 2026 - **Also known as:** GHSA-8wx2-9q48-vm9r, UBUNTU-CVE-2020-5398 ## What is CVE-2020-5398? CVE-2020-5398 is a high-severity vulnerability in Netapp Data Availability Services, published on 16 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a "Content-Disposition" header in the response where the filename attribute is derived from user supplied input. Weakness: CWE-494 (Download of Code Without Integrity Check), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2020-5398? 12 open source packages ship an affected version, including org.springframework:spring-webflux and org.springframework:spring-webmvc. It affects 33 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework:spring-webflux` | Maven | From 5.0.0.RELEASE | 5.0.16.RELEASE | | `org.springframework:spring-webflux` | Maven | From 5.0.0.RELEASE | 5.0.16.RELEASE | | `org.springframework:spring-webflux` | Maven | From 5.1.0.RELEASE | 5.1.13.RELEASE | | `org.springframework:spring-webflux` | Maven | From 5.1.0.RELEASE | 5.1.13.RELEASE | | `org.springframework:spring-webflux` | Maven | From 5.2.0.RELEASE | 5.2.3.RELEASE | | `org.springframework:spring-webflux` | Maven | From 5.2.0.RELEASE | 5.2.3.RELEASE | | `org.springframework:spring-webmvc` | Maven | From 5.0.0.RELEASE | 5.0.16.RELEASE | | `org.springframework:spring-webmvc` | Maven | From 5.0.0.RELEASE | 5.0.16.RELEASE | | `org.springframework:spring-webmvc` | Maven | From 5.1.0.RELEASE | 5.1.13.RELEASE | | `org.springframework:spring-webmvc` | Maven | From 5.1.0.RELEASE | 5.1.13.RELEASE | | `org.springframework:spring-webmvc` | Maven | From 5.2.0.RELEASE | 5.2.3.RELEASE | | `org.springframework:spring-webmvc` | Maven | From 5.2.0.RELEASE | 5.2.3.RELEASE | Products: Netapp Data Availability Services, Netapp Snapcenter, Oracle Application Testing Suite, Oracle Communications Billing and Revenue Management Elastic Charging Engine, Oracle Communications Cloud Native Core Policy, Oracle Communications Diameter Signaling Router, Oracle Communications Element Manager, Oracle Communications Policy Management, Oracle Communications Session Report Manager, Oracle Communications Session Route Manager, Oracle Enterprise Manager Base Platform, Oracle Financial Services Regulatory Reporting With Agilereporter, Oracle Flexcube Private Banking, Oracle Healthcare Master Person Index, Oracle Insurance Calculation Engine, Oracle Insurance Policy Administration J2ee, Oracle Insurance Rules Palette, Oracle Mysql, Oracle Rapid Planning, Oracle Retail Assortment Planning and 13 more. ## How do I fix CVE-2020-5398? Upgrade org.springframework:spring-webflux to a fixed version for your release line: 5.0.16.RELEASE, 5.1.13.RELEASE or 5.2.3.RELEASE. ## Is CVE-2020-5398 being exploited? There is no known exploitation of CVE-2020-5398 in the wild and no public exploit code. Public exploit code: - CVE-2020-5398 - RFD(Reflected File Download) Attack for Spring MVC (github_poc): https://github.com/motikan2010/CVE-2020-5398 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-5398 and fix it if it is affected. What it is: CVE-2020-5398 is a high-severity vulnerability in Netapp Data Availability Services, published on 16 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2020-5398 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework:spring-webflux (Maven): affected from 5.0.0.RELEASE; fixed in 5.0.16.RELEASE - org.springframework:spring-webflux (Maven): affected from 5.0.0.RELEASE; fixed in 5.0.16.RELEASE - org.springframework:spring-webflux (Maven): affected from 5.1.0.RELEASE; fixed in 5.1.13.RELEASE - org.springframework:spring-webflux (Maven): affected from 5.1.0.RELEASE; fixed in 5.1.13.RELEASE - org.springframework:spring-webflux (Maven): affected from 5.2.0.RELEASE; fixed in 5.2.3.RELEASE - org.springframework:spring-webflux (Maven): affected from 5.2.0.RELEASE; fixed in 5.2.3.RELEASE - org.springframework:spring-webmvc (Maven): affected from 5.0.0.RELEASE; fixed in 5.0.16.RELEASE - org.springframework:spring-webmvc (Maven): affected from 5.0.0.RELEASE; fixed in 5.0.16.RELEASE - org.springframework:spring-webmvc (Maven): affected from 5.1.0.RELEASE; fixed in 5.1.13.RELEASE - org.springframework:spring-webmvc (Maven): affected from 5.1.0.RELEASE; fixed in 5.1.13.RELEASE - org.springframework:spring-webmvc (Maven): affected from 5.2.0.RELEASE; fixed in 5.2.3.RELEASE - org.springframework:spring-webmvc (Maven): affected from 5.2.0.RELEASE; fixed in 5.2.3.RELEASE 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-2020-5398/ (Markdown: https://insights.sbomify.com/CVE-2020-5398/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5398 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5398 - OSV: https://osv.dev/vulnerability/CVE-2020-5398 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-5398/ Summaries are generated and may contain mistakes; the official description above is the record.