{"metadata": {"vulnerability": "CVE-2019-20790", "count": 21, "kinds": {"milestone": 5, "sighting": 2, "kev": 0, "other": 14}}, "data": [{"timestamp": "2020-04-27T00:00:00Z", "date_only": true, "value": "2020-04-27", "kind": "other", "label": "Pubdate", "source": "gsd \u00b7 GSD-2019-20790", "record": "GSD-2019-20790", "field": "namespaces.gitlab.com.advisories.0.pubdate"}, {"timestamp": "2020-04-27T00:00:00Z", "date_only": false, "value": "2020-04-27T00:00:00.000Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2019-20790", "field": "cveMetadata.dateReserved"}, {"timestamp": "2020-04-27T14:00:46Z", "date_only": false, "value": "2020-04-27T14:00:46.000Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2019-20790", "field": "cveMetadata.datePublished"}, {"timestamp": "2020-04-27T14:15:00Z", "date_only": false, "value": "2020-04-27T14:15:00Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-6PPH-69RG-FPW6", "record": "GHSA-6PPH-69RG-FPW6", "field": "database_specific.nvd_published_at"}, {"timestamp": "2020-04-27T14:15:00Z", "date_only": false, "value": "2020-04-27T14:15:00Z", "kind": "milestone", "label": "Published", "source": "osv_ubuntu \u00b7 UBUNTU-CVE-2019-20790", "record": "UBUNTU-CVE-2019-20790", "field": "published"}, {"timestamp": "2020-04-27T14:15:00Z", "date_only": false, "value": "2020-04-27T14:15Z", "kind": "other", "label": "Published Date", "source": "gsd \u00b7 GSD-2019-20790", "record": "GSD-2019-20790", "field": "namespaces.nvd.nist.gov.publishedDate"}, {"timestamp": "2020-04-27T14:15:11.127Z", "date_only": false, "value": "2020-04-27T14:15:11.127", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2019-20790", "record": "FKIE_CVE-2019-20790", "field": "published"}, {"timestamp": "2020-04-28T00:00:00Z", "date_only": true, "value": "2020-04-28", "kind": "other", "label": "Submit Time", "source": "cnvd \u00b7 CNVD-2020-27488", "record": "CNVD-2020-27488", "field": "submitTime"}, {"timestamp": "2020-05-04T00:00:00Z", "date_only": true, "value": "2020-05-04", "kind": "other", "label": "Date", "source": "gsd \u00b7 GSD-2019-20790", "record": "GSD-2019-20790", "field": "namespaces.gitlab.com.advisories.0.date"}, {"timestamp": "2020-05-10T00:00:00Z", "date_only": true, "value": "2020-05-10", "kind": "other", "label": "Open Time", "source": "cnvd \u00b7 CNVD-2020-27488", "record": "CNVD-2020-27488", "field": "openTime"}, {"timestamp": "2021-05-31T03:06:12Z", "date_only": false, "value": "2021-05-31T03:06:12.000Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / mitre", "record": "CVE-2019-20790", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2022-05-24T17:16:33Z", "date_only": false, "value": "2022-05-24T17:16:33Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-6PPH-69RG-FPW6", "record": "GHSA-6PPH-69RG-FPW6", "field": "published"}, {"timestamp": "2022-11-16T03:18:00Z", "date_only": false, "value": "2022-11-16T03:18Z", "kind": "other", "label": "Last Modified Date", "source": "gsd \u00b7 GSD-2019-20790", "record": "GSD-2019-20790", "field": "namespaces.nvd.nist.gov.lastModifiedDate"}, {"timestamp": "2022-11-16T12:00:19Z", "date_only": false, "value": "2022-11-16T12:00:19Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-6PPH-69RG-FPW6", "record": "GHSA-6PPH-69RG-FPW6", "field": "modified"}, {"timestamp": "2023-12-13T01:23:42.688Z", "date_only": false, "value": "2023-12-13T01:23:42.688951Z", "kind": "other", "label": "Updated", "source": "gsd \u00b7 GSD-2019-20790", "record": "GSD-2019-20790", "field": "gsd.osvSchema.modified"}, {"timestamp": "2024-08-05T02:53:09.236Z", "date_only": false, "value": "2024-08-05T02:53:09.236Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2019-20790", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2024-08-05T02:53:09.236Z", "date_only": false, "value": "2024-08-05T02:53:09.236Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / CVE", "record": "CVE-2019-20790", "field": "containers.adp.0.providerMetadata.dateUpdated"}, {"timestamp": "2026-06-17T02:31:12.060Z", "date_only": false, "value": "2026-06-17T02:31:12.060", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2019-20790", "record": "FKIE_CVE-2019-20790", "field": "lastModified"}, {"timestamp": "2026-09-01T20:01:59.605Z", "date_only": false, "value": "2026-09-01T20:01:59.605402Z", "kind": "sighting", "label": "Seen", "source": "https://t.me/hacking_Attack/38673", "record": "CVE-2019-20790", "field": "creation_timestamp", "uuid": "4b2695b1-5d64-4f8a-a89d-f8a9b2014f28", "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", "url": "https://t.me/hacking_Attack/38673"}, {"timestamp": "2026-09-06T13:00:05.209Z", "date_only": false, "value": "2026-09-06T13:00:05.209476Z", "kind": "sighting", "label": "Published proof of concept", "source": "https://t.me/hacking_Attack/38673", "record": "CVE-2019-20790", "field": "creation_timestamp", "uuid": "f409078b-3996-4cf1-b506-169ccb0d29b9", "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", "url": "https://t.me/hacking_Attack/38673"}, {"timestamp": "2026-10-17T09:06:57Z", "date_only": false, "value": "2026-10-17T09:06:57Z", "kind": "other", "label": "Updated", "source": "osv_ubuntu \u00b7 UBUNTU-CVE-2019-20790", "record": "UBUNTU-CVE-2019-20790", "field": "modified"}]}