Closed p5pRT closed 5 years ago
FYI.
-R
Forwarded Conversation Subject: [perlorg/perlweb] Perl source code archive perl-5.28.0.tar.gz triggers CVE2015-1592 alert in McAfee (#280)
From: TheRoundOne \notifications@​github\.com Date: Wed\, Oct 3\, 2018 at 7:50 AM To: perlorg/perlweb \perlweb@​noreply\.github\.com Cc: Subscribed \subscribed@​noreply\.github\.com
The file *dist/Storable/t/CVE-2015-1592.inc* triggers a trojan alert in the McAfee scanner. The file performs a test if the vulnerability is still present and the alert is a false positive.
It would be helpful to report this false positive to McAfee so they can update their database.
Alternatively\, the file could be obfuscated and re-assembled as part of the build\, so that this process does not have to be repeated for every release.
— You are receiving this because you are subscribed to this thread. Reply to this email directly\, view it on GitHub \https://github.com/perlorg/perlweb/issues/280, or mute the thread \https://github.com/notifications/unsubscribe-auth/AACo16B_bbUzpz3aLkyc88hlFlQifQlcks5uhM6ngaJpZM4XGMyL .
From: TheRoundOne \notifications@​github\.com Date: Wed\, Oct 3\, 2018 at 7:51 AM To: perlorg/perlweb \perlweb@​noreply\.github\.com Cc: Subscribed \subscribed@​noreply\.github\.com
I ran the archive through Virustotal.com and only McAfee of 49 scanners reported this issue.
From: Peter John Acklam \notifications@​github\.com Date: Fri\, Nov 30\, 2018 at 11:45 PM To: perlorg/perlweb \perlweb@​noreply\.github\.com Cc: Subscribed \subscribed@​noreply\.github\.com
The file triggers a pop-up on my computer:
Symantec Endpoint Protection Notification:
Scan type: Auto-Protect Scan Event: Risk Found! Security risk detected: Hacktool File: C:\src\perl\dist\perl-5.28.0-x86_64-9AbTH5QuUX.tmp\perl-5.28.0\dist\Storable\t\CVE-2015-1592.inc Location: C:\src\perl\dist\perl-5.28.0-x86_64-9AbTH5QuUX.tmp\perl-5.28.0\dist\Storable\t (…) Action taken: Pending Side Effects Analysis : Access denied Date found: 1. desember 2018 08:43:29
On Sat\, 01 Dec 2018 10:12:18 -0800\, robert wrote:
FYI.
Maybe remove the packaged exploit code entirely\, instead test the detection logic\, per the attached patch.
I'll apply this in a couple of days unless someone objects.
Since this isn't actually a security issue in perl\, it doesn't need a CVE or a release pushed. I'll make the ticket public when I apply the patch (or anyone can make it public sooner.)
Tony
The RT System itself - Status changed from 'new' to 'open'
On Sun\, 02 Dec 2018 21:25:01 -0800\, tonyc wrote:
On Sat\, 01 Dec 2018 10:12:18 -0800\, robert wrote:
FYI.
Maybe remove the packaged exploit code entirely\, instead test the detection logic\, per the attached patch.
I'll apply this in a couple of days unless someone objects.
Applied as fb5f378b17e3b41db03064c19b9205db64a3354c with an improved commit message.
Tony
@tonycoz - Status changed from 'open' to 'pending release'
Thank you for filing this report. You have helped make Perl better.
With the release today of Perl 5.30.0\, this and 160 other issues have been resolved.
Perl 5.30.0 may be downloaded via: https://metacpan.org/release/XSAWYERX/perl-5.30.0
If you find that the problem persists\, feel free to reopen this ticket.
@khwilliamson - Status changed from 'pending release' to 'resolved'
Migrated from rt.perl.org#133706 (status was 'resolved')
Searchable as RT133706$