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

Email Spoofing Leads to Financial and Reputation/Trust Loss #3

Open
ngpentest007 opened this issue Jul 30, 2019 · 0 comments
Open

Email Spoofing Leads to Financial and Reputation/Trust Loss #3

ngpentest007 opened this issue Jul 30, 2019 · 0 comments

Comments

@ngpentest007
Copy link

Hi Joey,

As discussed over telegram, Please find the vulnerability details below:

Vulnerability: Email Spoofing Leads to Financial and Reputation/Trust Loss

Description: It was observed that the domain is configured with Hardfail SPF Record to protect against Email spoofing but SPF is not a full proof solution and required DMARC Record to protect the email spoofing. At present the domain is lacking DMARC record which means an attacker can spoof ANY email.
For testing, I spoofed [email protected]

Vulnerable Application/Domain: fusion.org

Severity: High, easy to exploit

Impact: This allows an adversary to spoof an email to ask the user to perform sensitive actions such as stealing password, fraud money transaction, promotions, KYC Documents submission etc.
An attacker can also spoof CEO email id any perform malicious actions. An attacker can use any scenario :)

Screenshots: Attached, shows email spoofed WITHOUT spelling mistake which means even educated users will trust this email.
Email
Email 2

Fix: Generate a DMARC Record (p=reject) and then follow the below steps:
A) If you have direct access to manage DNS for your domain through an online DNS administration tool, look for a section to publish a TXT record or a section specific to DMARC records.
B) If you have access to manage DNS for your domain through a web hosting online administrative interface, look for DNS Settings and a place to enter a TXT record or a DMARC record.
C) If your company manages its DNS internally you may need to submit a request to publish the DNS record through your company's DNS management team.
D) If a third party hosts DNS for your domain you may need to submit a ticket with them to update the domain's DNS settings.

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