Bug 853906 (CVE-2002-2439)
Summary: | CVE-2002-2439 gcc: Integer overflow can occur during the computation of the memory region size for new[] operator | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Jan Lieskovsky <jlieskov> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | bressers, jakub, law, mfranc, mpolacek |
Target Milestone: | --- | Keywords: | Reopened, Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gcc 4.8.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-20 18:26:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 853918, 853919 | ||
Bug Blocks: | 853928 |
Description
Jan Lieskovsky
2012-09-03 09:54:49 UTC
This issue affects the versions of the gcc package, as shipped with Fedora release of 16 and 17. Please schedule an update. -- This issue affects the versions of the compat-gcc-34 packages, as shipped with Fedora release of 16 and 17. Please schedule an update. Created compat-gcc-34 tracking bugs for this issue Affects: fedora-all [bug 853919] Created gcc tracking bugs for this issue Affects: fedora-all [bug 853918] Reproducer (from http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351#c0): ----------------------------------------------------------------------- #include <testsuite_hooks.h> struct foo { char data[16]; void* operator new[] (size_t size) { VERIFY(size != sizeof(foo)); VERIFY (false); return malloc(size); } }; int main() { size_t size = size_t (-1) / sizeof(foo) + 2; try { foo* f = new foo[size]; VERIFY (f == 0); VERIFY (false); } catch(std::bad_alloc&) { return 0; } } I'm going to close this bug. It's fixed upstream, but not something we can backport without creating issues. |