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

Incorrect Recommendation for Double Encryption in OWASP M5: Insecure Communication #66

Open
pinpinsec opened this issue Sep 25, 2024 · 0 comments

Comments

@pinpinsec
Copy link

The OWASP Mobile Top 10 2023 documentation under M5-Insecure Communication states: "Apply a separate layer of encryption to any sensitive data before it is given to the SSL channel."
(If possible, apply a separate layer of encryption to any sensitive data before it is given to the SSL channel. In the event that future vulnerabilities are discovered in the SSL implementation, the encrypted data will provide a secondary defense against confidentiality violation.)

This advice could introduce security risks. Double encryption can prevent security appliances like WAFs from detecting malicious payloads. If an attacker modifies traffic, the secondary encryption layer might prevent proper inspection, allowing malicious traffic to reach the server undetected.

This suggestion contradicts the principle of effective traffic monitoring and inspection, particularly for mobile applications where WAFs are crucial in detecting manipulated traffic

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

1 participant