-
Notifications
You must be signed in to change notification settings - Fork 82
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
What is the need to redirect to harvest creds? #1
Comments
Hi Jeff, that is actually a valid point. It is possible to send directly the contents of However, you lose certain features by hardcoding the form directly into the e-mail:
Also, this proof of concept was meant only to demonstrate the redirect vulnerability, not to showcase credentials harvesting. The vulnerability can be used for anything that requires HTML tags not supported by Mail.app. |
All of those are good points, mainly #1 and the last part about being able to use other HTML tags that aren't supported. Good find and I appreciate the quick response. |
Hi everybody, im working in the perfect cloning of actual iCloud index login page, in a few days i sharing to you... please be patients. Nice Project, now its running on my server. |
There is a reason why the iCloud login dialog doesn't already look identical to the real thing. The reason is that this repository is not meant to be ready-to-use kit to scam people. It is a proof-of-concept, with the dialog styled just similarly enough to the real thing to get the attention it needed to get the issue fixed. Please do not create pull requests with enhancements to the dialog's looks. |
I don't quite understand how this example shows that http-equiv enables credential harvesting. Even without using redirection, you can simply send a form that is styled like the iCloud login in an email to harvest credentials. Sure, the redirection adds a bit of a lag which improves the believability but thats about it from what I can tell. Please correct me if I'm wrong or if anyone can think of other malicious use cases when allowing http-equiv in the Mail app. Sorry I posted this as an issue but I wasn't sure where to have this conversation..
The text was updated successfully, but these errors were encountered: