From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/unrar: bump to version 7.2.7
Date: Mon, 17 Aug 2026 22:26:49 +0200 [thread overview]
Message-ID: <aoNuO__aQMnMl0ni@windsurf> (raw)
In-Reply-To: <20260713113710.1732927-1-chakrabortyshubham66@gmail.com>
Hello,
On Mon, Jul 13, 2026 at 05:07:07PM +0530, Shubham Chakraborty wrote:
> Upstream does not provide a per-release change log for the unrarsrc
> tarball itself, only for WinRAR. Fixed from Repology/rarlab that
> 7.2.7 is the latest unrarsrc release available at:
>
> - https://www.rarlab.com/rar/unrarsrc-7.2.7.tar.gz
> - https://www.rarlab.com/WhatsNew.txt
>
> While at it, mark CVE-2022-30333 as ignored, since it was already
> fixed upstream in 6.1.2 and is falsely flagged by buildroot autobuilder for this
> package.
>
> Fixes CVE-2022-30333 (false positive, patched since 6.1.2/6.1.7).
> - https://nvd.nist.gov/vuln/detail/CVE-2022-30333
> - https://security-tracker.debian.org/tracker/CVE-2022-30333
Where do you see as being flagged affecting unrar in Buildroot? The
NVD database says this CVE affects versions up to 6.12. We're using
7.2.7, so we're not vulnerable.
https://security.buildroot.org/master/component/unrar doesn't show any
known vulnerability.
Could you clarify?
Best regards,
Thomas
--
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
prev parent reply other threads:[~2026-08-17 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 11:37 [Buildroot] [PATCH] package/unrar: bump to version 7.2.7 Shubham Chakraborty
2026-08-17 20:26 ` 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=aoNuO__aQMnMl0ni@windsurf \
--to=buildroot@buildroot.org \
--cc=chakrabortyshubham66@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox