From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wget: bump version to 1.25.0
Date: Sat, 14 Dec 2024 12:01:56 +0100 [thread overview]
Message-ID: <87h676ttnf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87seqtxhsw.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Thu, 12 Dec 2024 12:27:27 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Bernd" == Bernd Kuhls <bernd@kuhls.net> writes:
>> Release notes:
>> https://lists.gnu.org/archive/html/bug-wget/2024-11/msg00002.html
>> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> Committed, thanks.
It turns out that this fixes two security vulnerabilites, so I've
updated the commit message and applied to 2024.02.x and 2024.11.x,
thanks.
- CVE-2024-38428: url.c in GNU Wget through 1.24.5 mishandles semicolons in
the userinfo subcomponent of a URI, and thus there may be insecure
behavior in which data that was supposed to be in the userinfo
subcomponent is misinterpreted to be part of the host subcomponent.
https://nvd.nist.gov/vuln/detail/CVE-2024-38428
- CVE-2024-10524: Applications that use Wget to access a remote resource
using shorthand URLs and pass arbitrary user credentials in the URL are
vulnerable. In these cases attackers can enter crafted credentials which
will cause Wget to access an arbitrary host.
https://www.openwall.com/lists/oss-security/2024/11/18/6
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-12-14 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 19:29 [Buildroot] [PATCH 1/1] package/wget: bump version to 1.25.0 Bernd Kuhls
2024-12-12 11:27 ` Peter Korsgaard
2024-12-14 11:01 ` 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=87h676ttnf.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.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 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.