Security flaw fixed in mpg123 1.25.10 release: libmpg123: Fix another invalid read and segfault on damaged (fuzzed) files with part2_3_length == 0 (set maxband=1, pulled from upcoming 1.26.0). References: http://www.mpg123.de/cgi-bin/news.cgi
fedora 28, 29 and rawhide have 1.25.10.
Upstream Patch: http://www.mpg123.de/cgi-bin/scm/mpg123?view=revision&sortby=date&revision=4373
Looking at the source code, my guess is that this may not apply back to the mpg123 shipped in rhel-7. It looks like the maxband parameter wasn't set to 0 until a later commit and underwent quite a bit of refactoring. (http://www.mpg123.de/cgi-bin/scm/mpg123/trunk/src/libmpg123/layer3.c?sortby=date&r1=4355&r2=4356&pathrev=4373&).
Created mpg123 tracking bugs for this issue: Affects: epel-7 [bug 1627848] Affects: fedora-all [bug 1627847]