Skip to content

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

High severity GitHub Reviewed Published Jan 6, 2022 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven com.softwaremill.akka-http-session:core_2.12 (Maven)

Affected versions

>= 0.3.0, < 0.6.1

Patched versions

0.6.1

Description

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.

References

Published by the National Vulnerability Database Jan 20, 2021
Reviewed Mar 22, 2021
Published to the GitHub Advisory Database Jan 6, 2022
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.121%
(47th percentile)

Weaknesses

CVE ID

CVE-2020-28452

GHSA ID

GHSA-4jf5-jggp-g56j

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.