From oss security: A security flaw was found in the way librdmacm, a userspace RDMA Communication Managment API allowing to specify connections using TCP/IP addresses even though it opens RDMA specific connections, performed binding to the underlying ib_acm service (librdmacm used default port value of 6125 to bind to ib_acm service). An attacker able to run a rogue ib_acm service could use this flaw to make librdmacm applications to use potentially bogus address resolution information. References: https://bugzilla.redhat.com/show_bug.cgi?id=865483 Upstream patch: http://git.openfabrics.org/git?p=~shefty/librdmacm.git;a=commitdiff;h=4b5c1aa734e0e734fc2ba3cd41d0ddf02170af6d Credit: This issue was discovered by Florian Weimer of Red Hat Product Security Team.
CVE-2012-4516 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-4516): librdmacm 1.0.16, when ibacm.port is not specified, connects to port 6125, which allows remote attackers to specify the address resolution information for the application via a malicious ib_acm service.
I think there's a bump available, otherwise patch available at http://git.openfabrics.org/git?p=~shefty/ibacm.git;a=commit;h=c7d28b35d64333c262de3ec972c426423dadccf9
@maintainers, please cleanup vulnerable version 1.0.16 in tree. 1.0.18 is already stable. Once cleaned feel free to close this bug. GLSA Vote: No
Maintainer timeout: commit 035a23105ef01cea6cb94b96abb3e666dae547b8 Author: Aaron Bauman <bman@gentoo.org> Date: Tue Mar 29 15:54:30 2016 +0900 sys-infiniband/librdmacm: cleanup vulnerable packages per 438444 Package-Manager: portage-2.2.26
Should have reviewed the package a bit more. Restored. @maintainer, please do a proper cleanup of the package. Thanks.
Old versions removed from tree
(In reply to Alexey Shvetsov from comment #6) > Old versions removed from tree Thanks so much, Alexey!