From: Peter Korsgaard <peter@korsgaard.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nginx: security bump to 1.30.3
Date: Thu, 02 Jul 2026 18:53:58 +0200 [thread overview]
Message-ID: <87fr21nxi1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <akYVJ5F5kodcxrfK@waldemar-brodkorb.de> (Waldemar Brodkorb's message of "Thu, 2 Jul 2026 09:37:11 +0200")
>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:
> Changes with nginx 1.30.3
> *) Security: a heap memory buffer overflow might occur in a worker
> process when using a configuration with "ignore_invalid_headers off;"
> and "large_client_header_buffers" with large configured values when
> proxying a specially crafted request to HTTP/2 or gRPC backend,
> allowing an attacker to cause worker process memory corruption or
> segmentation fault in a worker process (CVE-2026-42055).
> Thanks to Mufeed VH of Winfunc Research.
> *) Security: a heap memory buffer overread might occur in a worker
> process while handling a specially sent response with decoding from
> UTF-8 via the "charset_map" directive, allowing an attacker to cause
> a limited disclosure of worker proccess memory or segmentation fault
> in a worker process (CVE-2026-48142).
> Thanks to Han Yan of Xiaomi and p4p3r of CYBERONE.
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-02 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 7:37 [Buildroot] [PATCH] package/nginx: security bump to 1.30.3 Waldemar Brodkorb
2026-07-02 16:53 ` Peter Korsgaard [this message]
2026-07-10 13:52 ` Thomas Perale via buildroot
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=87fr21nxi1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=wbx@openadk.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