Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 865510

Summary:	CVE-2012-4516 librdmacm: Tried to connect to port 6125 if ibacm.port was not found [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Jan Lieskovsky <jlieskov>
Component:	librdmacm	Assignee:	Doug Ledford <dledford>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	17	CC:	dledford
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-15 18:06:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	752665, 865483

Description Jan Lieskovsky 2012-10-11 15:53:12 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
versions.

For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When creating a Bodhi update request, please include this bug ID and the
bug IDs of this bug's parent bugs filed against the "Security Response"
product (the top-level CVE bugs).  Please mention the CVE IDs being fixed
in the RPM changelog when available.

Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=865483

Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please ensure that it is only closed
when all affected versions are fixed.

[bug automatically created by: add-tracking-bugs]

Comment 1 Fedora Update System 2012-12-06 19:11:58 UTC

librdmacm-1.0.17-0.gitc6bfc1c.1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/librdmacm-1.0.17-0.gitc6bfc1c.1.fc18

Comment 2 Fedora Update System 2012-12-06 19:12:08 UTC

librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/librdmacm-1.0.17-0.gitc6bfc1c.1.fc17

Comment 3 Fedora Update System 2012-12-07 03:25:34 UTC

Package librdmacm-1.0.17-0.gitc6bfc1c.1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing librdmacm-1.0.17-0.gitc6bfc1c.1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19892/librdmacm-1.0.17-0.gitc6bfc1c.1.fc17
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-12-15 18:06:12 UTC

librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2013-01-12 01:06:58 UTC

librdmacm-1.0.17-0.gitc6bfc1c.1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.