From: fus@plutonium24.de
To: gcc-help@gcc.gnu.org
Subject: determining impact of vulnerability CVE-2022-27943 in libiberty/rust-demangle.c
Date: Tue, 02 Aug 2022 18:11:26 +0200 [thread overview]
Message-ID: <28f5239fb7e8c8f029104563393310dd@plutonium24.de> (raw)
The above mentioned CVE
(https://nvd.nist.gov/vuln/detail/CVE-2022-27943) just specifies GNU GCC
11.2 to be affected, but fails to eplicitly specify that previous
versions are not affected. Does this CVE only affect exactly GCC version
11.2?
And I would also like to know how I can determine whether or not I will
be eposed to this vulnerability when using an affected version. Is the
rust demangler used internally by any C/C++ tools or will I only be
affected when compiling rust programs?
Regards
Frank
next reply other threads:[~2022-08-02 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 16:11 fus [this message]
2022-08-02 16:33 ` Jonathan Wakely
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=28f5239fb7e8c8f029104563393310dd@plutonium24.de \
--to=fus@plutonium24.de \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).