Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulnerability on Saved Card #210

Open
Djohel opened this issue Oct 18, 2024 · 2 comments
Open

Vulnerability on Saved Card #210

Djohel opened this issue Oct 18, 2024 · 2 comments

Comments

@Djohel
Copy link

Djohel commented Oct 18, 2024

Hey !

A flaw in access control has been identified in the management of pre-registered cards by users of the Saferpay module. By exploiting this flaw, a user can register on the web application, enter their payment card (e.g., VISA), and then use another user's card from the application to pay for their own cart.

First, it is necessary to register your payment card for future purchases. Then, you simply need to select it via the associated menu.
image

When the payment request is issued, the "selectedCreditCard_VISA" parameter references the identifier of this card. By modifying it during the interception of the HTTP request, another user's card will be used.
Note: The identifier used to reference the card is incremental and can be trivially determined by an attacker. It is recommended to use identifiers such as UUIDv4, which are random and not predictable by other users.
image

Note : I use BURP app to do this.
The Saferpay module then redirects the user to the 3D Secure mechanism associated with the fraudulently selected card.

Implement an access control mechanism on pre-registered card identifiers based on the current user's session token would prevent it.
We did a fix but you may foud a better way to solve this issue :
image

If you need more information, feel free to ask!

Thank you!

@justelis22
Copy link
Collaborator

Hi there,
Thank you for the detailed description!

We will check this issue and I will get back to you as soon as more details.

Thank you for your patience!

--
Best Regards,
Invertus Support team.

@justelis22
Copy link
Collaborator

Thank you for the feedback @Djohel,

We have already implemented this fix, and it will be added to the upcoming release. The fixes for this release were focused on the card-saving functionality, so it was very good timing.

If you have any questions, please let me know!

Best Regards,
Invertus Support team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants