Adplug <= 2.0 and CVS <= 2006-07-04 is reportedly affected by various heap and
stack overflow vulnerabilities. No CVE id Yet.
Solved by upgrading to the new upstream version.
Thanks for bringing this to attention, Ville!
I hope not too many systems were compromised by
rouge AdLib songs ;-)
Thanks for the fix, but please be careful with shared library sonames in the
future. Packages built against the old one and depending on it are likely to
prevent the new fixed library package from being installed.
Yeah, sorry I know, in this case I happened to maintain all affected packages
so just rebuilt them.
However, a first timer the question arise: how do I properly retire an .so file
with security vulnerabilities? (Cannot find a good idea in any guidelines.)
(In reply to comment #4)
> Yeah, sorry I know, in this case I happened to maintain all affected packages
Yes, but only in FE. 3rd party repositories and local packages which use the
libs are affected too.
> However, a first timer the question arise: how do I properly retire an .so
> file with security vulnerabilities? (Cannot find a good idea in any
If doable and feasible, backporting only the security fixes and avoiding the
soname change would be one way of handling it smoothly.
An incompatible upgrade policy and instructions are slowly in the works, but so
far there is no consensus except that the very least one should do is to send a
mail to fedora-maintainers, notifying about the issue, beforehand if at all
possible so others (including non-FC/FE packagers) can prepare.
Here's one example which IMO is being handled well.