Skip to content
Fencer Intel
medium 6.3

CVE-2020-28452 json

Cross-site Request Forgery (CSRF)

published 5y ago modified 4mo ago also GHSA-4jf5-jggp-g56j , EUVD-2022-0445

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

This affects the package com.softwaremill.akka-http-session:core_2.12 from 0 and before 0.6.1; all versions of package com.softwaremill.akka-http-session:core_2.11; the package com.softwaremill.akka-http-session:core_2.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.

Patch / fix

  • maven com.softwaremill.akka-http-session:core_2.12 0.6.1
  • n/a com.softwaremill.akka-http-session:core_2.12 0.6.1
  • n/a com.softwaremill.akka-http-session:core_2.13 0.6.1

Is CVE-2020-28452 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven com.softwaremill.akka-http-session:core_2.12
>=0.3.0, <0.6.1
0.6.1

Affected products

  • n/a com.softwaremill.akka-http-session:core_2.12
  • n/a com.softwaremill.akka-http-session:core_2.11
  • n/a com.softwaremill.akka-http-session:core_2.13

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.