From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] libcurl: Version bump. 7.83.0 -> 7.83.1
Date: Wed, 11 May 2022 09:20:28 +0200 [thread overview]
Message-ID: <20220511072028.1152041-1-christian.melki@t2data.com> (raw)
Usual churn of fixes.
Curl is seeing an accelerated CVE ticketing.
Probably due to a functioning bug bounty program.
https://hackerone.com/curl?type=team
With 30 reports in the last 90 days.
So probably expect more CVEs in the near future.
Changelog: https://curl.se/changes.html
Security: https://curl.se/docs/security.html
Plugs CVEs: CVE-2022-30115, CVE-2022-27782, CVE-2022-27781,
CVE-2022-27780, CVE-2022-27779, CVE-2022-27778
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/libcurl.make | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rules/libcurl.make b/rules/libcurl.make
index 3840b2abd..8faa948bf 100644
--- a/rules/libcurl.make
+++ b/rules/libcurl.make
@@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBCURL) += libcurl
#
# Paths and names
#
-LIBCURL_VERSION := 7.83.0
-LIBCURL_MD5 := b7924acdea33dedc3150a044789ed0bb
+LIBCURL_VERSION := 7.83.1
+LIBCURL_MD5 := 08c6d9c25d9cf8d17be28363753e42ca
LIBCURL := curl-$(LIBCURL_VERSION)
LIBCURL_SUFFIX := tar.xz
LIBCURL_URL := https://curl.haxx.se/download/$(LIBCURL).$(LIBCURL_SUFFIX)
--
2.34.1
next reply other threads:[~2022-05-11 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 7:20 Christian Melki [this message]
2022-05-11 10:49 ` Alexander Dahl
2022-05-13 8:35 ` Michael Olbrich
2022-05-13 8:42 ` Christian Melki
2022-05-13 12:49 ` Michael Olbrich
2022-05-25 9:45 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20220511072028.1152041-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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