# CVE-2020-7780: Cross-site Request Forgery (CSRF) > Attackers can bypass CSRF protection in Akka HTTP session library by sending empty headers and cookies, requiring specific configuration. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 27 Nov 2020 - **Updated:** 17 Sep 2024 - **Also known as:** GHSA-q42q-523g-3fwv ## What is CVE-2020-7780? CVE-2020-7780 is a medium-severity vulnerability in com.softwaremill.akka-http-session:core_2.11, published on 27 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description This affects the package com.softwaremill.akka-http-session:core_2.13 before 0.5.11; the package com.softwaremill.akka-http-session:core_2.12 before 0.5.11; the package com.softwaremill.akka-http-session:core_2.11 before 0.5.11. For older versions, endpoints protected by randomTokenCsrfProtection could be bypassed with an empty X-XSRF-TOKEN header and an empty XSRF-TOKEN cookie. Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2020-7780? 6 open source packages ship an affected version, including com.softwaremill.akka-http-session:core_2.11, com.softwaremill.akka-http-session:core_2.12 and com.softwaremill.akka-http-session:core_2.13. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.softwaremill.akka-http-session:core_2.11` | Maven | All versions | 0.5.11 | | `com.softwaremill.akka-http-session:core_2.11` | Maven | All versions | 0.5.11 | | `com.softwaremill.akka-http-session:core_2.12` | Maven | All versions | 0.5.11 | | `com.softwaremill.akka-http-session:core_2.12` | Maven | All versions | 0.5.11 | | `com.softwaremill.akka-http-session:core_2.13` | Maven | All versions | 0.5.11 | | `com.softwaremill.akka-http-session:core_2.13` | Maven | All versions | 0.5.11 | Products: Softwaremill Akka-Http-Session. ## How do I fix CVE-2020-7780? Upgrade com.softwaremill.akka-http-session:core_2.11 to 0.5.11 or later. ## Is CVE-2020-7780 being exploited? There is no known exploitation of CVE-2020-7780 in the wild and no public exploit code. ## Other vulnerabilities in com.softwaremill.akka-http-session:core_2.11 - [CVE-2020-28452](https://insights.sbomify.com/CVE-2020-28452/): Cross-site Request Forgery (CSRF) (medium 6.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-7780 and fix it if it is affected. What it is: CVE-2020-7780 is a medium-severity vulnerability in com.softwaremill.akka-http-session:core_2.11, published on 27 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2020-7780 in the wild and no public exploit code. Affected packages and fixed versions: - com.softwaremill.akka-http-session:core_2.11 (Maven): affected all versions; fixed in 0.5.11 - com.softwaremill.akka-http-session:core_2.11 (Maven): affected all versions; fixed in 0.5.11 - com.softwaremill.akka-http-session:core_2.12 (Maven): affected all versions; fixed in 0.5.11 - com.softwaremill.akka-http-session:core_2.12 (Maven): affected all versions; fixed in 0.5.11 - com.softwaremill.akka-http-session:core_2.13 (Maven): affected all versions; fixed in 0.5.11 - com.softwaremill.akka-http-session:core_2.13 (Maven): affected all versions; fixed in 0.5.11 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-7780/ (Markdown: https://insights.sbomify.com/CVE-2020-7780/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7780 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7780 - OSV: https://osv.dev/vulnerability/CVE-2020-7780 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-7780/ Summaries are generated and may contain mistakes; the official description above is the record.