GNU gcc 4.1

CPE Details

GNU gcc 4.1
gnu
gcc
4.1
2007-08-23
19h16 +00:00
2007-09-14
15h36 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:gnu:gcc:4.1:*:*:*:*:*:*:*

Informations

Vendor

gnu

Product

gcc

Version

4.1

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2021-37322 2021-11-18 20h11 +00:00 GCC c++filt v2.26 was discovered to contain a use-after-free vulnerability via the component cplus-dem.c.
7.8
High
CVE-2002-2439 2019-10-23 15h47 +00:00 Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts.
7.8
High
CVE-2019-15847 2019-09-02 20h03 +00:00 The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __builtin_darn intrinsic into a single call, thus reducing the entropy of the random number generator. This occurred because a volatile operation was not specified. For example, within a single execution of a program, the output of every __builtin_darn() call may be the same.
7.5
High
CVE-2018-12886 2019-05-22 16h42 +00:00 stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.
8.1
High
CVE-2015-5276 2015-11-17 14h00 +00:00 The std::random_device class in libstdc++ in the GNU Compiler Collection (aka GCC) before 4.9.4 does not properly handle short reads from blocking sources, which makes it easier for context-dependent attackers to predict the random values via unspecified vectors.
5
CVE-2006-1902 2006-04-20 08h00 +00:00 fold_binary in fold-const.c in GNU Compiler Collection (gcc) 4.1 improperly handles pointer overflow when folding a certain expr comparison to a corresponding offset comparison in cases other than EQ_EXPR and NE_EXPR, which might introduce buffer overflow vulnerabilities into applications that could be exploited by context-dependent attackers.NOTE: the vendor states that the essence of the issue is "not correctly interpreting an offset to a pointer as a signed value."
2.1