Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 351996 - media-sound/pms _FORTIFY_SOURCE indicates presence of overflow
Summary: media-sound/pms _FORTIFY_SOURCE indicates presence of overflow
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Mykyta Holubakha
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: fortify-source
  Show dependency tree
 
Reported: 2011-01-18 11:26 UTC by Diego Elio Pettenò (RETIRED)
Modified: 2016-08-25 20:16 UTC (History)
2 users (show)

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


Attachments
Build log (pms-0.42:20110118-094321.log,10.42 KB, text/plain)
2011-01-18 11:27 UTC, Diego Elio Pettenò (RETIRED)
Details
Patch (0001-media-sound-pms-fix-a-buffer-overflow.patch,834 bytes, patch)
2016-08-14 11:54 UTC, Mykyta Holubakha
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Elio Pettenò (RETIRED) gentoo-dev 2011-01-18 11:26:51 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.

Thanks,
Your friendly neighborhood tinderboxer
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2011-01-18 11:27:04 UTC
Created attachment 260131 [details]
Build log
Comment 2 Pacho Ramos gentoo-dev 2016-08-14 08:40:34 UTC
please remember to reassign the bugs when taking the package
Comment 3 Mykyta Holubakha 2016-08-14 11:54:51 UTC
Created attachment 443288 [details, diff]
Patch

Attached is a patch, which fixes the warning, by specifying the correct constant.
Comment 4 Mykyta Holubakha 2016-08-14 12:09:56 UTC
The changes in the bug probably require a revbump.

Shall I file a new ticket with a revbump, which would incorporate the changes, as well as changes proposed in #526530?