GitHub - MrTiz/CVE-2023-35671: Android App Pin Security Issue Allowing Unauthorized Payments via Google Wallet
github.com
Android App Pin Security Issue Allowing Unauthorized Payments via Google Wallet - GitHub - MrTiz/CVE-2023-35671: Android App Pin Security Issue Allowing Unauthorized Payments via Google Wallet

There is a possible way for a general purpose NFC reader to read the full card number and expiry details when the device is in locked screen mode due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Google has calculated a high severity for this vulnerability.

  • The_Hunted_One@beehaw.org
    1·
    1 year ago

    From what I’ve seen here the vulnerability exposes card number and expiration details. I don’t know enough about NFC payment authorization to confidently confirm, but I’m not sure what other information would constitute an authorization

    • d3Xt3r@beehaw.org
      1·
      1 year ago

      From @SuperIce@lemmy.world:

      If the PoS supports tokens, it’ll use unique tokens for each payment. If the PoS doesn’t support tokens, the phone has a virtual credit card number linked to the real one, so if it does get stolen, you can just remove the card from your Google Wallet to deactivate it. Your real card number is never exposed.

      Even then, credit card numbers on their own aren’t that useful anymore. Any online payment needs the CVC and PoS devices usually require chip or tap cards, which don’t use the number. On top of that, credit card companies have purchase price restrictions when using swipe because of the security risks vs chip (which is why most PoS devices don’t support swipe anymore).