Skip to content

Solana Pay Vulnerable to Weakness in Transfer Validation Logic

Moderate severity GitHub Reviewed Published Jul 28, 2022 in anza-xyz/solana-pay • Updated Jan 27, 2023

Package

npm @solana/pay (npm)

Affected versions

<= 0.2.0

Patched versions

0.2.1

Description

Description

When a Solana Pay transaction is located using a reference key, it may be checked to represent a transfer of the desired amount to the recipient, using the supplied validateTransfer function. An edge case regarding this mechanism could cause the validation logic to validate multiple transfers.

Impact

Most known Solana Pay point of sale applications are currently run on physical point of sale devices, which makes this issue unlikely to occur. However, there may be web-based point of sale applications using the protocol where it may be more likely to occur.

Patches

This issue has been patched as of version 0.2.1. Users of the Solana Pay SDK should upgrade to it.

References

@jordaaash jordaaash published to anza-xyz/solana-pay Jul 28, 2022
Published by the National Vulnerability Database Aug 1, 2022
Published to the GitHub Advisory Database Aug 6, 2022
Reviewed Aug 6, 2022
Last updated Jan 27, 2023

Severity

Moderate

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
Unchanged
Confidentiality
None
Integrity
Low
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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.078%
(35th percentile)

Weaknesses

CVE ID

CVE-2022-35917

GHSA ID

GHSA-j47c-j42c-mwqq

Source code

Credits

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