Skip to content

← Public intelligence

Maven package

com.softwaremill.akka-http-session:core_2.12

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.8MavenPublished

    Cross-Site Request Forgery

    CVE-2020-7780 · GHSA-q42q-523g-3fwv

    Affected
    • Maven com.softwaremill.akka-http-session:core_2.12 < 0.5.11
    Fixed in
    0.5.11· Vendor fix available
    Issue
    This affects the package com.softwaremill.akka-http-session:core2.13 before 0.5.11; the package com.softwaremill.akka-http-session:core2.12 before 0.5.11; the package com.softwaremill.akka-http-session:core2.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.

    Recommended action: Upgrade to 0.5.11 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.8MavenPublished

    Cross-Site Request Forgery in com.softwaremill.akka-http-session:core_2.12

    CVE-2020-28452 · GHSA-4jf5-jggp-g56j

    Affected
    • Maven com.softwaremill.akka-http-session:core_2.12 >= 0.3.0, < 0.6.1
    Fixed in
    0.6.1· Vendor fix available
    Issue
    This affects the package com.softwaremill.akka-http-session:core2.12 from 0 and before 0.6.1; all versions of package com.softwaremill.akka-http-session:core2.11; the package com.softwaremill.akka-http-session:core2.13 from 0 and before 0.6.1. CSRF protection can be bypassed by forging a request that contains the same value for both the X-XSRF-TOKEN header and the XSRF-TOKEN cookie value, as the check in randomTokenCsrfProtection only checks that the two values are equal and non-empty.

    Recommended action: Upgrade to 0.6.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →