You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@apache.org by "Kevin A. McGrail" <km...@apache.org> on 2018/09/16 16:59:12 UTC
[SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Apache SpamAssassin 3.4.2 was recently released [1], and fixes several
issues of security note.
First, a denial of service vulnerability that exists in all modern versions.
The vulnerability arises with certain unclosed tags in emails that cause
markup to be handled incorrectly leading to scan timeouts.
In Apache SpamAssassin, using HTML::Parser, we setup an object and hook
into the begin and end tag event handlers In both cases, the "open"
event is immediately followed by a "close" event - even if the tag *does
not* close in the HTML being parsed.
Because of this, we are missing the "text" event to deal with the object
normally. This can cause carefully crafted emails that might take more
scan time than expected leading to a Denial of Service.
The issue is possibly a bug or design decision in HTML::Parser that
specifically impacts the way Apache SpamAssassin uses the module with
poorly formed html.
The exploit has been seen in the wild but not believe to have been
purposefully part of a Denial of Service attempt. We are concerned that
there may be attempts to abuse the vulnerability in the future.
Therefore, we strongly recommend all users of these versions upgrade to
Apache SpamAssassin 3.4.2 as soon as possible.
This issue has been assigned CVE id CVE-2017-15705 [2].
Second, this release also fixes a reliance on "." in @INC in one
configuration script. Whether this can be exploited in any way is
uncertain.
This issue has been assigned CVE id CVE-2016-1238 [3].
Third, this release fixes a potential Remote Code Execution bug with the
PDFInfo plugin. Thanks to cPanel Security Team for their report of this
issue.
This issue has been assigned CVE id CVE-2018-11780 [4].
Fourth, this release fixes a local user code injection in the meta rule
syntax. Thanks again to cPanel Security Team for their report of this issue.
This issue has been assigned CVE id CVE-2018-11781 [5].
To contact the Apache SpamAssassin security team, please e-mail
security at spamassassin.apache.org. For more information about Apache
SpamAssassin, visit the http://spamassassin.apache.org/ web site.
Apache SpamAssassin Security Team
[1]:
https://lists.apache.org/thread.html/1ac11532235b5459aa16c4e9d636bf4aa0b141d347d1361e40cc1b78@%3Cannounce.apache.org%3E
[2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15705
[3]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1238
[4]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11780
[5]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11781
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by Kenneth Porter <sh...@sewingwitch.com>.
On 9/16/2018 5:44 PM, Kevin A. McGrail wrote:
> Thanks for the post. The bug is way out of line though.
Earlier bug that should probably be the one tracked:
https://bugzilla.redhat.com/show_bug.cgi?id=1629474
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by "Kevin A. McGrail" <km...@apache.org>.
Reindl,
I question whether I should bother rewarding your bad behavior and again
ask.you if you find your negative attitude gets you where you want to be in
life? But for others, here are the facts and the policy.
"we see that you mentioned these CVE names public at
https://lists.apache.org/thread.html/a3dc4c9d2a942d550e834df8f423eedeb042fdb69f4a83df26f1446b@%3Cdev.spamassassin.apache.org%3E
Once names are mentioned in public it starts a clock and we usually have 24
hours to send the information to Mitre, see process at
https://apache.org/security/committers.html"
That was 4 days ago and we worked the process with ethical disclosures and
attention to good security hygiene.
Spend your energy elsewhere as I dnftec.
On Sun, Sep 16, 2018, 22:26 Reindl Harald <h....@thelounge.net> wrote:
>
>
> Am 17.09.18 um 02:44 schrieb Kevin A. McGrail:
> > Thanks for the post. The bug is way out of line though.
> >
> > We posted release candidate 1 on the 12th noting the 4 CVE issues
> > coming. I also backchanneled with RH as a heads up. We do have a
> brain...
>
> no you don't or why is the httpd project capable to bring CVE details a
> few days *after* release anncouncement (besides that they manage
> regulary releases at all)
>
> what you do with that way of announcemnt is trigger pressure for no good
> reason
>
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by "Kevin A. McGrail" <km...@apache.org>.
Thanks for the post. The bug is way out of line though.
We posted release candidate 1 on the 12th noting the 4 CVE issues coming.
I also backchanneled with RH as a heads up. We do have a brain...
I have 3.4.2 installed on centos 7 and it was drop-in other than the redhat
specific paths, systemd, config locations, etc.
Hopefully they will push the new version. A backport is not going to be
easy.
On Sun, Sep 16, 2018, 19:34 Kenneth Porter <sh...@sewingwitch.com> wrote:
> Here's the Red Hat Bugzilla bug requesting a new package for Fedora/RHEL
> be issued ASAP:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1629491
>
> Once the official package drops, you should be able to download the SRPM
> here:
>
>
> https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/SRPMS/Packages/s/
>
> The 3.4.1 package is there as I type this, and I see it has a lot of
> patches marked 3.4.1. So it's probably not as easy as just dropping the
> 3.4.2 tarball into it.
>
>
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by Kenneth Porter <sh...@sewingwitch.com>.
Here's the Red Hat Bugzilla bug requesting a new package for Fedora/RHEL
be issued ASAP:
https://bugzilla.redhat.com/show_bug.cgi?id=1629491
Once the official package drops, you should be able to download the SRPM
here:
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/SRPMS/Packages/s/
The 3.4.1 package is there as I type this, and I see it has a lot of
patches marked 3.4.1. So it's probably not as easy as just dropping the
3.4.2 tarball into it.
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by "Kevin A. McGrail" <km...@apache.org>.
Per the asf security team, mitre considers the public rc1 from a few days
ago as the start of the clock for the publishing so we were already way
past the 24 hour windiw.
Hopefully, the announcements and reports are obfuscated and bugzilla ia
private so it'll be contained.
On Sun, Sep 16, 2018, 16:59 Reindl Harald <h....@thelounge.net> wrote:
> i doubt that it is wiese to blwo out security notes *that short* after
> release and *that long* after the last release
>
> Am 16.09.18 um 18:59 schrieb Kevin A. McGrail:
> > Apache SpamAssassin 3.4.2 was recently released [1], and fixes several
> > issues of security note.
> >
> > First, a denial of service vulnerability that exists in all modern
> versions.
> >
> > The vulnerability arises with certain unclosed tags in emails that cause
> > markup to be handled incorrectly leading to scan timeouts.
> >
> > In Apache SpamAssassin, using HTML::Parser, we setup an object and hook
> > into the begin and end tag event handlers In both cases, the "open"
> > event is immediately followed by a "close" event - even if the tag *does
> > not* close in the HTML being parsed.
> >
> > Because of this, we are missing the "text" event to deal with the object
> > normally. This can cause carefully crafted emails that might take more
> > scan time than expected leading to a Denial of Service.
> >
> > The issue is possibly a bug or design decision in HTML::Parser that
> > specifically impacts the way Apache SpamAssassin uses the module with
> > poorly formed html.
> >
> > The exploit has been seen in the wild but not believe to have been
> > purposefully part of a Denial of Service attempt. We are concerned that
> > there may be attempts to abuse the vulnerability in the future.
> > Therefore, we strongly recommend all users of these versions upgrade to
> > Apache SpamAssassin 3.4.2 as soon as possible.
> >
> > This issue has been assigned CVE id CVE-2017-15705 [2].
> >
> >
> > Second, this release also fixes a reliance on "." in @INC in one
> > configuration script. Whether this can be exploited in any way is
> > uncertain.
> >
> > This issue has been assigned CVE id CVE-2016-1238 [3].
> >
> >
> > Third, this release fixes a potential Remote Code Execution bug with the
> > PDFInfo plugin. Thanks to cPanel Security Team for their report of this
> > issue.
> >
> > This issue has been assigned CVE id CVE-2018-11780 [4].
> >
> >
> > Fourth, this release fixes a local user code injection in the meta rule
> > syntax. Thanks again to cPanel Security Team for their report of this
> issue.
> >
> > This issue has been assigned CVE id CVE-2018-11781 [5].
> >
> >
> > To contact the Apache SpamAssassin security team, please e-mail
> > security at spamassassin.apache.org. For more information about Apache
> > SpamAssassin, visit the http://spamassassin.apache.org/ web site.
> >
> > Apache SpamAssassin Security Team
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/1ac11532235b5459aa16c4e9d636bf4aa0b141d347d1361e40cc1b78@%3Cannounce.apache.org%3E
> >
> > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15705
> >
> > [3]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1238
> >
> > [4]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11780
> >
> > [5]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11781
>
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by "Kevin A. McGrail" <km...@apache.org>.
Per the asf security team, mitre considers the public rc1 from a few days
ago as the start of the clock for the publishing so we were already way
past the 24 hour windiw.
Hopefully, the announcements and reports are obfuscated and bugzilla ia
private so it'll be contained.
On Sun, Sep 16, 2018, 16:59 Reindl Harald <h....@thelounge.net> wrote:
> i doubt that it is wiese to blwo out security notes *that short* after
> release and *that long* after the last release
>
> Am 16.09.18 um 18:59 schrieb Kevin A. McGrail:
> > Apache SpamAssassin 3.4.2 was recently released [1], and fixes several
> > issues of security note.
> >
> > First, a denial of service vulnerability that exists in all modern
> versions.
> >
> > The vulnerability arises with certain unclosed tags in emails that cause
> > markup to be handled incorrectly leading to scan timeouts.
> >
> > In Apache SpamAssassin, using HTML::Parser, we setup an object and hook
> > into the begin and end tag event handlers In both cases, the "open"
> > event is immediately followed by a "close" event - even if the tag *does
> > not* close in the HTML being parsed.
> >
> > Because of this, we are missing the "text" event to deal with the object
> > normally. This can cause carefully crafted emails that might take more
> > scan time than expected leading to a Denial of Service.
> >
> > The issue is possibly a bug or design decision in HTML::Parser that
> > specifically impacts the way Apache SpamAssassin uses the module with
> > poorly formed html.
> >
> > The exploit has been seen in the wild but not believe to have been
> > purposefully part of a Denial of Service attempt. We are concerned that
> > there may be attempts to abuse the vulnerability in the future.
> > Therefore, we strongly recommend all users of these versions upgrade to
> > Apache SpamAssassin 3.4.2 as soon as possible.
> >
> > This issue has been assigned CVE id CVE-2017-15705 [2].
> >
> >
> > Second, this release also fixes a reliance on "." in @INC in one
> > configuration script. Whether this can be exploited in any way is
> > uncertain.
> >
> > This issue has been assigned CVE id CVE-2016-1238 [3].
> >
> >
> > Third, this release fixes a potential Remote Code Execution bug with the
> > PDFInfo plugin. Thanks to cPanel Security Team for their report of this
> > issue.
> >
> > This issue has been assigned CVE id CVE-2018-11780 [4].
> >
> >
> > Fourth, this release fixes a local user code injection in the meta rule
> > syntax. Thanks again to cPanel Security Team for their report of this
> issue.
> >
> > This issue has been assigned CVE id CVE-2018-11781 [5].
> >
> >
> > To contact the Apache SpamAssassin security team, please e-mail
> > security at spamassassin.apache.org. For more information about Apache
> > SpamAssassin, visit the http://spamassassin.apache.org/ web site.
> >
> > Apache SpamAssassin Security Team
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/1ac11532235b5459aa16c4e9d636bf4aa0b141d347d1361e40cc1b78@%3Cannounce.apache.org%3E
> >
> > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15705
> >
> > [3]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1238
> >
> > [4]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11780
> >
> > [5]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11781
>
Re: [SECURITY] Apache SpamAssassin 3.4.2 resolves CVE-2017-15705,
CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781
Posted by "Kevin A. McGrail" <km...@apache.org>.
Per the asf security team, mitre considers the public rc1 from a few days
ago as the start of the clock for the publishing so we were already way
past the 24 hour windiw.
Hopefully, the announcements and reports are obfuscated and bugzilla ia
private so it'll be contained.
On Sun, Sep 16, 2018, 16:59 Reindl Harald <h....@thelounge.net> wrote:
> i doubt that it is wiese to blwo out security notes *that short* after
> release and *that long* after the last release
>
> Am 16.09.18 um 18:59 schrieb Kevin A. McGrail:
> > Apache SpamAssassin 3.4.2 was recently released [1], and fixes several
> > issues of security note.
> >
> > First, a denial of service vulnerability that exists in all modern
> versions.
> >
> > The vulnerability arises with certain unclosed tags in emails that cause
> > markup to be handled incorrectly leading to scan timeouts.
> >
> > In Apache SpamAssassin, using HTML::Parser, we setup an object and hook
> > into the begin and end tag event handlers In both cases, the "open"
> > event is immediately followed by a "close" event - even if the tag *does
> > not* close in the HTML being parsed.
> >
> > Because of this, we are missing the "text" event to deal with the object
> > normally. This can cause carefully crafted emails that might take more
> > scan time than expected leading to a Denial of Service.
> >
> > The issue is possibly a bug or design decision in HTML::Parser that
> > specifically impacts the way Apache SpamAssassin uses the module with
> > poorly formed html.
> >
> > The exploit has been seen in the wild but not believe to have been
> > purposefully part of a Denial of Service attempt. We are concerned that
> > there may be attempts to abuse the vulnerability in the future.
> > Therefore, we strongly recommend all users of these versions upgrade to
> > Apache SpamAssassin 3.4.2 as soon as possible.
> >
> > This issue has been assigned CVE id CVE-2017-15705 [2].
> >
> >
> > Second, this release also fixes a reliance on "." in @INC in one
> > configuration script. Whether this can be exploited in any way is
> > uncertain.
> >
> > This issue has been assigned CVE id CVE-2016-1238 [3].
> >
> >
> > Third, this release fixes a potential Remote Code Execution bug with the
> > PDFInfo plugin. Thanks to cPanel Security Team for their report of this
> > issue.
> >
> > This issue has been assigned CVE id CVE-2018-11780 [4].
> >
> >
> > Fourth, this release fixes a local user code injection in the meta rule
> > syntax. Thanks again to cPanel Security Team for their report of this
> issue.
> >
> > This issue has been assigned CVE id CVE-2018-11781 [5].
> >
> >
> > To contact the Apache SpamAssassin security team, please e-mail
> > security at spamassassin.apache.org. For more information about Apache
> > SpamAssassin, visit the http://spamassassin.apache.org/ web site.
> >
> > Apache SpamAssassin Security Team
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/1ac11532235b5459aa16c4e9d636bf4aa0b141d347d1361e40cc1b78@%3Cannounce.apache.org%3E
> >
> > [2]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15705
> >
> > [3]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1238
> >
> > [4]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11780
> >
> > [5]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-11781
>