{"vulnerability": "CVE-2020-12272", "sightings": [{"uuid": "11800560-914a-4ee3-ab57-c23109e183bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-12272", "type": "seen", "source": "https://t.me/hacking_Attack/38673", "content": "Bugs found with this tool    Gmail.com DMARC bypass demo video, https://youtu.be/xuKZpT0rsd0  Outlook.com DMARC bypass video, https://youtu.be/IsWgAEbPaK0  Yahoo.com DMARC bypass video, https://youtu.be/DRepfStOruE  Protonmail.com DMARC bypass video,\u00a0https://youtu.be/bh4_SoPniMA  CVE-2020-12272, OpenDMARC bypass bug report, https://sourceforge.net/p/opendmarc/tickets/237/  CVE-2019-20790, OpenDMARC and pypolicyd-spf bypass bug report, https://sourceforge.net/p/opendmarc/tickets/235/  Mail.ru DMARC bypass bug report on HackerOne, https://hackerone.com/reports/731878    Welcome to send a pull request to file your bug report here.  Q&A    How do I know if the email has bypassed DMARC authentication successfully?    You can check it in the Authentication-results header in the raw message headers. If the header shows dmarc=pass, it means the email has passed the DMARC authentication. \u00a0You can check some demos video here (https://www.youtube.com/playlist?list=PL--A-gWJV1dJ19SyhkzklMC3C8ra1kK5-).    Why do emails fail to send?    There are several possible reasons if you fail to send an email: 1) your ISP blocks outgoing emails to port 25 to prevent spam. In this case, you need to ask for permission from the ISP; 2) the IP address is in the spam list of the target email services. In many cases, you resolve the problem here, https://www.spamhaus.org/lookup/ ; \u00a03) some email services check if there is a PTR record for the sending IP, you may also need to set the PTR record to bypass this check; 4) the email cannot pass the format validation of the target email service, you may want to try a different test case.    Why the email goes to the spam folder? Any way to avoid this?    Currently, espoofer focuses on bypassing SPF/DKIM/DMARC authentication and doesn't aim for spam filter bypass. But you could try to use a reputable sending IP address, domain, and benign message content to bypass the spam filter.    Why I send an email successfully but the email didn't show up\u00a0in either inbox or spam folder?    In our prior experiences, some email services filter suspicious emails silently.    When testing server_a5/a6, why I cannot set specical characters like \"(\" in the domain?    You will need to set up your own authority DNS server, rather than use third-party DNS hosting services,  as some DNS hosting services have restrictions on setting specical characters. See issue (https://github.com/chenjj/espoofer/issues/2#issuecomment-686918954).  Credits  Welcome to add more test cases.  \n\nDownload Espoofer (https://github.com/chenjj/espoofer)\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:59.478424Z"}, {"uuid": "fecd98de-89a7-46b8-8e99-52acc891c559", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-12272", "type": "seen", "source": "https://t.me/hacking_Attack/38673", "content": "Bugs found with this tool    Gmail.com DMARC bypass demo video, https://youtu.be/xuKZpT0rsd0  Outlook.com DMARC bypass video, https://youtu.be/IsWgAEbPaK0  Yahoo.com DMARC bypass video, https://youtu.be/DRepfStOruE  Protonmail.com DMARC bypass video,\u00a0https://youtu.be/bh4_SoPniMA  CVE-2020-12272, OpenDMARC bypass bug report, https://sourceforge.net/p/opendmarc/tickets/237/  CVE-2019-20790, OpenDMARC and pypolicyd-spf bypass bug report, https://sourceforge.net/p/opendmarc/tickets/235/  Mail.ru DMARC bypass bug report on HackerOne, https://hackerone.com/reports/731878    Welcome to send a pull request to file your bug report here.  Q&A    How do I know if the email has bypassed DMARC authentication successfully?    You can check it in the Authentication-results header in the raw message headers. If the header shows dmarc=pass, it means the email has passed the DMARC authentication. \u00a0You can check some demos video here (https://www.youtube.com/playlist?list=PL--A-gWJV1dJ19SyhkzklMC3C8ra1kK5-).    Why do emails fail to send?    There are several possible reasons if you fail to send an email: 1) your ISP blocks outgoing emails to port 25 to prevent spam. In this case, you need to ask for permission from the ISP; 2) the IP address is in the spam list of the target email services. In many cases, you resolve the problem here, https://www.spamhaus.org/lookup/ ; \u00a03) some email services check if there is a PTR record for the sending IP, you may also need to set the PTR record to bypass this check; 4) the email cannot pass the format validation of the target email service, you may want to try a different test case.    Why the email goes to the spam folder? Any way to avoid this?    Currently, espoofer focuses on bypassing SPF/DKIM/DMARC authentication and doesn't aim for spam filter bypass. But you could try to use a reputable sending IP address, domain, and benign message content to bypass the spam filter.    Why I send an email successfully but the email didn't show up\u00a0in either inbox or spam folder?    In our prior experiences, some email services filter suspicious emails silently.    When testing server_a5/a6, why I cannot set specical characters like \"(\" in the domain?    You will need to set up your own authority DNS server, rather than use third-party DNS hosting services,  as some DNS hosting services have restrictions on setting specical characters. See issue (https://github.com/chenjj/espoofer/issues/2#issuecomment-686918954).  Credits  Welcome to add more test cases.  \n\nDownload Espoofer (https://github.com/chenjj/espoofer)\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:21.887739Z"}]}