All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/drogon: fix CVE-2023-26137 and CVE-2023-26138
Date: Tue, 27 Oct 2026 18:22:33 +0100	[thread overview]
Message-ID: <auDd1axP1bPiv1os@windsurf> (raw)
In-Reply-To: <20261027151809.1110228-1-dario.binacchi@amarulasolutions.com>

On Tue, Oct 27, 2026 at 04:18:09PM +0100, Dario Binacchi wrote:
> All drogon releases, including 1.9.14, are affected by two CRLF
> injection vulnerabilities, which upstream has fixed but not released
> yet.
> 
> - CVE-2023-26137: HTTP response splitting when untrusted input is used
>   to build header values in addHeader() and addCookie().
>   https://www.cve.org/CVERecord?id=CVE-2023-26137
> - CVE-2023-26138: CRLF injection when untrusted input is used to set
>   request headers in addHeader().
>   https://www.cve.org/CVERecord?id=CVE-2023-26138
> 
> Backport the upstream fix, which rejects CR and LF characters in header
> and cookie values, both in responses and in requests sent by
> HttpClient.
> 
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>

Applied to master, thanks!

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-27 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 15:18 [Buildroot] [PATCH 1/1] package/drogon: fix CVE-2023-26137 and CVE-2023-26138 Dario Binacchi
2026-10-27 17:22 ` Thomas Petazzoni via buildroot [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=auDd1axP1bPiv1os@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.