As summary states, our stable emul-linux-x86-baselibs contain vulnerable openssl. I'm not sure if we should go into stabilizing 20140406-r1 that early. Alternatively, I think we could do a revbump of previous version with just openssl replaced (I think that SONAME didn't change).
I would stabilize latest version for sure (they work fine for me, not sure if one more test would be required)
(In reply to Pacho Ramos from comment #1) > I would stabilize latest version for sure (they work fine for me, not sure > if one more test would be required) CCing team then: app-emulation/emul-linux-x86-baselibs-20140406-r1 app-emulation/emul-linux-x86-compat-20140406 app-emulation/emul-linux-x86-cpplibs-20140406 app-emulation/emul-linux-x86-db-20140406 app-emulation/emul-linux-x86-gstplugins-20140406 app-emulation/emul-linux-x86-gtklibs-20140406 app-emulation/emul-linux-x86-gtkmmlibs-20140406 app-emulation/emul-linux-x86-jna-20140406 app-emulation/emul-linux-x86-medialibs-20140406 app-emulation/emul-linux-x86-motif-20140406 app-emulation/emul-linux-x86-opengl-20140406 app-emulation/emul-linux-x86-qtlibs-20140406 app-emulation/emul-linux-x86-sdl-20140406 app-emulation/emul-linux-x86-soundlibs-20140406 app-emulation/emul-linux-x86-xlibs-20140406
amd64 stable
Added to existing GLSA request.
This issue was resolved and addressed in GLSA 201412-11 at http://security.gentoo.org/glsa/glsa-201412-11.xml by GLSA coordinator Sean Amoss (ackle).