From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] perl: add upstream security fix for CVE-2018-12015
Date: Tue, 17 Jul 2018 09:31:43 +0200 [thread overview]
Message-ID: <87lgaal3mo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180612152130.32491-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 12 Jun 2018 17:21:30 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes CVE-2018-12015 - In Perl through 5.26.2, the Archive::Tar module
> allows remote attackers to bypass a directory-traversal protection
> mechanism, and overwrite arbitrary files, via an archive file containing a
> symlink and a regular file with the same name.
> Patch from
> https://github.com/jib/archive-tar-new/commit/ae65651eab053fc6dc4590dbb863a268215c1fc5
> with path rewritten to match perl tarball.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2018.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-07-17 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 15:21 [Buildroot] [PATCH] perl: add upstream security fix for CVE-2018-12015 Peter Korsgaard
2018-06-13 20:52 ` Thomas Petazzoni
2018-06-17 15:55 ` Peter Korsgaard
2018-07-17 7:31 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgaal3mo.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox