Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/libcurl: security bump to version 8.3.0
Date: Sun, 24 Sep 2023 23:32:22 +0200	[thread overview]
Message-ID: <87o7hrfeah.fsf@48ers.dk> (raw)
In-Reply-To: <20230917124914.2F93D87163@busybox.osuosl.org> (Yann E. MORIN's message of "Sun, 17 Sep 2023 14:41:04 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > commit:
 > https://git.buildroot.net/buildroot/commit/?id=56b066740608e9ca62ce5739fe1a683f7050b605
 > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

 > Fixes the following security issue:

 > CVE-2023-38039: HTTP headers eat all memory

 > When curl retrieves an HTTP response, it stores the incoming headers so that
 > they can be accessed later via the libcurl headers API.

 > However, curl did not have a limit on the size or quantity of headers it
 > would accept in a response, allowing a malicious server to stream an endless
 > series of headers to a client and eventually cause curl to run out of heap
 > memory.

 > https://curl.se/docs/CVE-2023-38039.html

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-09-24 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 12:41 [Buildroot] [git commit] package/libcurl: security bump to version 8.3.0 Yann E. MORIN
2023-09-24 21:32 ` 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=87o7hrfeah.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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