{"vulnerability": "CVE-2019-2079", "sightings": [{"uuid": "86791d8c-7215-421c-931b-6ca1f62904a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2019-20794", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "3710a6b3-01df-4a31-ae7d-53d4bcff3176", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-20799", "type": "seen", "source": "https://t.me/cibsecurity/12127", "content": "ATENTION\u203c New - CVE-2019-20799\n\nIn Cherokee through 1.2.104, multiple memory corruption errors may be used by a remote attacker to destabilize the work of a server.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-05-18T07:28:19.000000Z"}, {"uuid": "874207c8-cc88-47ec-96c0-d0ffa64eb527", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-20798", "type": "seen", "source": "https://t.me/cibsecurity/12128", "content": "ATENTION\u203c New - CVE-2019-20798\n\nAn XSS issue was discovered in handler_server_info.c in Cherokee through 1.2.104. The requested URL is improperly displayed on the About page in the default configuration of the web server and its administrator panel. The XSS in the administrator panel can be used to reconfigure the server and execute arbitrary commands.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-05-18T07:28:20.000000Z"}, {"uuid": "2919de6b-d6c0-4db8-acb1-7dc20aeb949a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-20797", "type": "seen", "source": "https://t.me/cibsecurity/12129", "content": "ATENTION\u203c New - CVE-2019-20797\n\nAn issue was discovered in e6y prboom-plus 2.5.1.5. There is a buffer overflow in client and server code responsible for handling received UDP packets, as demonstrated by I_SendPacket or I_SendPacketTo in i_network.c.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-05-18T07:28:24.000000Z"}, {"uuid": "4b2695b1-5d64-4f8a-a89d-f8a9b2014f28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-20790", "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.605402Z"}, {"uuid": "f409078b-3996-4cf1-b506-169ccb0d29b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-20790", "type": "published-proof-of-concept", "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-06T13:00:05.209476Z"}]}