Skip to content

TrueLayer.Client SSRF when fetching payment or payment provider

High severity GitHub Reviewed Published Jan 30, 2024 in TrueLayer/truelayer-dotnet • Updated Jan 30, 2024

Package

nuget TrueLayer.Client (NuGet)

Affected versions

< 1.6.0

Patched versions

1.6.0

Description

Impact

The vulnerability could potentially allow a malicious actor to gain control over the destination URL of the HttpClient used in the API classes. For applications using the SDK, requests to unexpected resources on local networks or to the internet could be made which could lead to information disclosure.

Patches

Versions of TrueLayer.Client v1.6.0 and later are not affected.

Workarounds

The issue can be mitigated by having strict egress rules limiting the destinations to which requests can be made, and applying strict validation to any user input passed to the TrueLayer.Client library.

References

@lboynton lboynton published to TrueLayer/truelayer-dotnet Jan 30, 2024
Published by the National Vulnerability Database Jan 30, 2024
Published to the GitHub Advisory Database Jan 30, 2024
Reviewed Jan 30, 2024
Last updated Jan 30, 2024

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
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS score

0.114%
(46th percentile)

Weaknesses

CVE ID

CVE-2024-23838

GHSA ID

GHSA-67m4-qxp3-j6hh

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.