Bug 1102900

Summary: CVE-2013-4159 ctdb: /tmp file vulnerability issues [fedora-all]
Product: [Fedora] Fedora Reporter: Kurt Seifried <kseifried>
Component: ctdbAssignee: Sumit Bose <sbose>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 20CC: adas, gdeschner, jarrpa, pj.pandit, sbose, ssorce
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: fst_ping=1
Fixed In Version: ctdb-2.5.4-2.fc20 Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-20 08:36:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 986773    

Description Kurt Seifried 2014-05-29 19:14:27 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

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

For more information see:

When creating a Bodhi update request, use the bodhi submission link noted
in the next comment(s).  This will include the bug IDs of this tracking
bug as well as the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

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

Comment 1 Kurt Seifried 2014-05-29 19:14:34 UTC
Use the following update submission link to create the Bodhi request for
this issue as it contains the top-level parent bug(s) as well as this
tracking bug.  This will ensure that all associated bugs get updated when
new packages are pushed to stable.

IMPORTANT: ensure that the "Close bugs when update is stable" option
remains checked.

Bodhi update submission link:

Comment 2 pjp 2014-12-03 18:27:59 UTC
Hello sbose,

Could you please fix this soon?

Comment 3 Sumit Bose 2014-12-04 10:01:10 UTC
Sorry, I lost track of this because the issue is fixed upstream and we already build packages with the latest upstream version, but forgot to push them to Bodhi. I just found an issue when checking if /tmp is really not used in the latest version and created a fixed package for rawhide. If Jose agrees with the change I 'll prepare update for F20 and F21 and push them to Bodhi with the link from comment #1.

Comment 4 pjp 2014-12-05 14:00:07 UTC
Cool, thank you.

Comment 5 Fedora Update System 2014-12-08 12:05:01 UTC
ctdb-2.5.4-2.fc20 has been submitted as an update for Fedora 20.

Comment 6 Jose A. Rivera 2014-12-11 14:56:10 UTC
Ah! Apologies for the delay. Yes, this looks like a good idea, I'll clear the needinfo flags. I see the f20 update attached to this, is f21 also taken care of?

Comment 7 Sumit Bose 2014-12-11 17:31:11 UTC
yes, I've build a new F21 version as well, but since F21 already had a 2.5.4 version where the /tmp issue is fixed, I didn't attached it to this ticket. JFYI the F21 update link is https://admin.fedoraproject.org/updates/ctdb-2.5.4-2.fc21 .

Comment 8 Fedora Update System 2014-12-12 04:29:43 UTC
Package ctdb-2.5.4-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ctdb-2.5.4-2.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2014-12-20 08:36:13 UTC
ctdb-2.5.4-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.