Bug 1207397

Summary:	CVE-2014-8119 netcf: augeas path expression injection via interface name [epel-5]
Product:	[Fedora] Fedora EPEL	Reporter:	Tomas Hoger <thoger>
Component:	netcf	Assignee:	Laine Stump <laine>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	el5	CC:	laine, thoger
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:	2017-04-06 10:16:52 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:	1172176

Description Tomas Hoger 2015-03-30 20:23:21 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 EPEL.

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:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided 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
fedpkg commit message.

epel-5 tracking bug for netcf: see blocks bug list for full details of the security issue(s).

This bug is never intended to be made public, please put any public notes
in the blocked bugs.

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

Comment 1 Tomas Hoger 2015-03-30 20:23:29 UTC

Use the following template to for the 'fedpkg update' request to submit an
update 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.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1172176,1207397

# Description of your update
notes=Security fix for CVE-2014-8119

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1172176,1207397

Comment 2 Laine Stump 2015-03-30 21:00:50 UTC

The netcf in EPEL-5 was never officially supported, and was deprecated (i.e. never again updated) in 2010, just about a year after netcf was first publicly released, because netcf began requiring libnl, which was not available for RHEL5/EPEL5 at the time. (Additionally, the main consumer of netcf's services is libvirt, and since the standard libvirt packages are built as a part of RHEL/CentOS they must be built without netcf support. So it is only those people who build their own libvirt from source (and happen to have installed netcf from EPEL5) who would ever potentially use netcf on RHEL5.

For those reasons I don't think it is necessary or a good use of time to attempt to backport the CVE patches to such an ancient version of netcf. I of course welcome other opinions :-)

Comment 3 Tomas Hoger 2015-03-30 21:16:28 UTC

Wontfix is an option, yes.  If it's really unused in epel-5 and not really relevant, there's option to obsolete / remote it completely.

Comment 4 Fedora End Of Life 2017-04-06 10:16:52 UTC

Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
is no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora
or Fedora EPEL, please feel free to reopen this bug against that version. If
you are unable to reopen this bug, please file a new report against the current
release. If you experience problems, please add a comment to this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.