Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 337239 - media-gfx/swftools _FORTIFY_SOURCE indicates presence of overflow
Summary: media-gfx/swftools _FORTIFY_SOURCE indicates presence of overflow
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: László Szalma
Keywords: NeedPatch
Depends on: 411265
Blocks: fortify-source
  Show dependency tree
Reported: 2010-09-14 09:10 UTC by Diego Elio Pettenò (RETIRED)
Modified: 2012-04-09 18:23 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Build log (swftools-0.9.0:20100914-005126.log,1021.03 KB, text/plain)
2010-09-14 09:11 UTC, Diego Elio Pettenò (RETIRED)
build.log (a.log,77.35 KB, text/plain)
2012-04-08 17:34 UTC, László Szalma

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Elio Pettenò (RETIRED) gentoo-dev 2010-09-14 09:10:42 UTC
You're receiving this bug because the package in Summary has produced _FORTIFY_SOURCE related warnings indicating the presence of a sure overflow in a static buffer.

Even though this is not always an indication of a security problem it might even be. So please check this out ASAP.

By the way, _FORTIFY_SOURCE is disabled when you disable optimisation, so don't try finding out the cause using -O0.

Your friendly neighborhood tinderboxer
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2010-09-14 09:11:13 UTC
Created attachment 247225 [details]
Build log
Comment 2 Pacho Ramos gentoo-dev 2012-02-26 16:10:37 UTC
Still valid with 0.9.1?
Comment 3 Pacho Ramos gentoo-dev 2012-04-06 19:32:53 UTC
Comment 4 Pacho Ramos gentoo-dev 2012-04-08 11:39:08 UTC
Reopening to try to know if this is fixed with latest version
Comment 5 László Szalma 2012-04-08 17:34:24 UTC
Created attachment 308231 [details]

There isn't any QA warning, or "will always overflow destination buffer" warning during compile.

I use

CFLAGS="-march=athlon64 -O2 -pipe -msse3"

So I think this potential security problem is fixed by upstream.