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 ibacm service (librdmacm used default port value of 6125 to bind to ibacm service). An attacker able to run a rogue ibacm service could use this flaw to make librdmacm applications to use potentially bogus address resolution information.

Upstream patch: [1] http://git.openfabrics.org/git?p=~shefty/librdmacm.git;a=commitdiff;h=4b5c1aa734e0e734fc2ba3cd41d0ddf02170af6d

Acknowledgements:

This issue was discovered by Florian Weimer of Red Hat Product Security Team.

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 ibacm service (librdmacm used default port value of 6125 to bind to ibacm service). An attacker able to run a rogue ibacm service could use this flaw to make librdmacm applications to use potentially bogus address resolution information.

Upstream patch: [1] http://git.openfabrics.org/git?p=~shefty/librdmacm.git;a=commitdiff;h=4b5c1aa734e0e734fc2ba3cd41d0ddf02170af6d

Acknowledgements:

This issue was discovered by Florian Weimer of Red Hat Product Security Team.