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

Asymmetric cipher with insecure padding used in android kotlin #2235

Open
vinaykumarIndia opened this issue Jan 3, 2025 · 2 comments
Open

Comments

@vinaykumarIndia
Copy link

vinaykumarIndia commented Jan 3, 2025

Describe the bug

  • I have implemented com.microsoft.identity.client:msal library:5.8.2 android kotlin i got a high security issue while test our apk :-
  • The app uses the RSA algorithm without Optimal Asymmetric Encryption Padding (OAEP), which weakens the encryption and,
Screenshot 2025-01-03 at 11 14 27 AM Screenshot 2025-01-03 at 11 14 43 AM therefore, makes it easier for the attackers to decrypt the data.
  • RSA encrypts the provided data deterministically. It means that when the same message and encryption key are used as input, the algorithm produces the same output ciphertext every time:

Smartphone (please complete the following information):

  • Android Version: 28+
  • MSAL Version - 5.8.2
@HanishaChowdary
Copy link

@vinaykumarIndia - could you please share more data on the references to Google Tink library here in this scenario?

@shahzaibj
Copy link
Contributor

@vinaykumarIndia Can you tell us more about the security issues / warnings you are getting? Which tool is generated these warnings? Is it inside Play Console? or some custom tool?

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

3 participants