Bug 1439662 (CVE-2017-5950)

Summary:	CVE-2017-5950 yaml-cpp: Stack overflow in HandleNode()
Product:	[Other] Security Response	Reporter:	Andrej Nemec <anemec>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	apevec, bkearney, cbillett, chrisw, cvsbot-xmlrpc, guido.grazioli, hhorak, hobbes1069, jjoyce, jmatthew, jorton, jschluet, lhh, lpeer, markmc, mmccune, ohadlevy, rbryant, rhos-maint, sclewis, tdecacqu, tlestach, tsanders
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-04 13:27:42 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:	1439675, 1439676, 1439677, 1439678, 1439679, 1469879
Bug Blocks:	1439664

Description Andrej Nemec 2017-04-06 11:41:37 UTC

The SingleDocParser::HandleNode function yaml-cpp does not limit the maximum recursion to a suitable amount. Remote attackers to cause a denial of service (stack consumption and application crash) via a crafted YAML file.

Upstream bug:

https://github.com/jbeder/yaml-cpp/issues/459

Comment 1 Andrej Nemec 2017-04-06 11:56:22 UTC

Created yaml-cpp tracking bugs for this issue:

Affects: epel-6 [bug 1439678]
Affects: epel-7 [bug 1439676]
Affects: fedora-all [bug 1439677]


Created yaml-cpp03 tracking bugs for this issue:

Affects: epel-7 [bug 1439679]
Affects: fedora-all [bug 1439675]

Comment 2 Stefan Cornelius 2017-06-29 14:57:49 UTC

It seems like MongoDB uses yaml for configuration files only, which is hardly a reasonable attack vector. Thus, I don't think that this yaml-cpp issue is a problem in a MongoDB context.

Comment 4 Product Security DevOps Team 2020-08-04 13:27:42 UTC

This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2017-5950