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 Server misconfiguration #2167

Closed
MrDottt opened this issue Dec 15, 2021 · 5 comments
Closed

Email Server misconfiguration #2167

MrDottt opened this issue Dec 15, 2021 · 5 comments
Labels
bug Not Ready security vulnerability An issue to raising awareness for security vulnerabilities

Comments

@MrDottt
Copy link

MrDottt commented Dec 15, 2021

Hi
There is another Email Server misconfiguration which is No valid SPF record
Vulnerable Domain: https://thenewboston.com
Vulnerability: No Valid SPF Records

Description:
There is an email spoofing vulnerability. Email spoofing is the forgery of an email header so that the message appears to have originated from someone or somewhere other than the actual source. Email spoofing is a tactic used in phishing and spam campaigns because people are more likely to open an email when they think it has been sent by a legitimate source. The goal of email spoofing is to get recipients to open, and possibly even respond to, a solicitation.

Step to reproduce:
SPF record lookup and validation

  1. GO TO- https://mxtoolbox.com
  2. ENTER your domain with an SPF command like: spf:thenewboston.com into the URL box and CLICK GO.
  3. You will see the result: No SPF Record found

Now the attacker can target some users - by sending some fake offers money bonus to claim the BTC or reward add PayPal card to following phishing site, or others trap what an attacker want, which can be harmful to users, so it needs to fix.

The attacker can easily send fake mail from the official @thenewboston.com thenewboston.com mail address https://emkei.cz/?reCAPTCHAv2
Impact: An attacker can send Fake mails to the thenewboston.com users. The results can be more dangerous.

Remediation: Replace ~all with -all to prevent fake email.

Reference:
https://hackerone.com/reports/629087
https://www.digitalocean.com/community/tutorials/how-to-use-an-spf-record-to-prevent-spoofing-improve-e-mail-reliability

Thank you.

@wakawakathedev wakawakathedev added the security vulnerability An issue to raising awareness for security vulnerabilities label Dec 21, 2021
@MrDottt
Copy link
Author

MrDottt commented Feb 2, 2022

Hi @wakawakathedev

Would you please let me know an update? It's been more than 40 days since I have reported that vulnerability.

Thank you
Have a nice day.

@wakawakathedev
Copy link
Contributor

Hi @MrDottt
I don't believe we use an email signup anymore for the website, so will have to check if this is still applicable.

There's another issue (for doing email) but need to link it

@wakawakathedev
Copy link
Contributor

#1268

@MrDottt
Copy link
Author

MrDottt commented Mar 22, 2022

Any update?

@wakawakathedev
Copy link
Contributor

@MrDottt we don't use emails in the website - I've escalated this to whoever maintains/owns the domain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not Ready security vulnerability An issue to raising awareness for security vulnerabilities
Projects
None yet
Development

No branches or pull requests

3 participants