![]() The challenge I set myself before submitting my report was to crack the encryption algorithm and view the raw card numbers.Ĭredit and debit card numbers use an internationally recognised standard. In order for the company to use them in future, I knew that they must be stored in a decryptable format. The application allowed users to store up to 10 payment cards on their account for easier checkout when buying products and services. ![]() This included: the cardholders name, their registered address, the expiry date of the card, the last 4 digits of the card, the type of card, and an encrypted version of the full credit card number. ![]() Using these guessed parameters, I was able to retrieve all credit cards added to a user’s account. By playing with the ‘about me’ graphql API request I was able to guess and retrieve all the logged-in user’s stored values present in the database, not just those disclosed by the web app. While hacking on a private bug bounty program, I found a graphql endpoint that exposed way more information about logged-in users than it should have done. Here’s how I cracked them to reveal the full card details. I found an API that exposed encrypted credit card numbers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |