From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a016c0ce6a1daa791353c8bb54383fb9b71be6ef
Date: Sun, 29 Oct 2017 18:34:38 +0000 [thread overview]
Message-ID: <20171029183439.1D63A1081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via a016c0ce6a1daa791353c8bb54383fb9b71be6ef (commit)
from 7dadc138292897979fd7b42dcaae3ea19f24dae0 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit a016c0ce6a1daa791353c8bb54383fb9b71be6ef
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Oct 29 18:33:03 2017 +0000
wget: Update to 1.19.2
Fixes CVE-2017-13089
A stack-based buffer overflow when processing chunked, encoded HTTP
responses was found in wget. By tricking an unsuspecting user into
connecting to a malicious HTTP server, an attacker could exploit
this flaw to potentially execute arbitrary code.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/wget | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/wget b/lfs/wget
index 8d3d13c..2c750bf 100644
--- a/lfs/wget
+++ b/lfs/wget
@@ -24,7 +24,7 @@
include Config
-VER = 1.19.1
+VER = 1.19.2
THISAPP = wget-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = d30d82186b93fcabb4116ff513bfa9bd
+$(DL_FILE)_MD5 = caabf9727fa429626316619a6369fffa
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-10-29 18:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171029183439.1D63A1081BCF@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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