Bug 1340830 (CVE-2016-1902)

Summary:	CVE-2016-1902 php-symfony: SecureRandom's fallback not secure when OpenSSL fails
Product:	[Other] Security Response	Reporter:	Andrej Nemec <anemec>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	anemec, fedora, james.hogarth, shawn
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	php-symfony 2.3.37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-02 08:15:27 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:	1340831
Bug Blocks:

Description Andrej Nemec 2016-05-30 11:26:51 UTC

The SecureRandom Symfony class goal is to generate secure random numbers. Several strategies are used depending on PHP's configuration. On PHP installations where the random_bytes() function is not available, Symfony falls back to using openssl_random_pseudo_bytes(). If that does not work, Symfony generates a secure random number using uniqid() and mt_rand(), which are not suitable for cryptographic contexts.

External references:

https://symfony.com/blog/cve-2016-1902-securerandom-s-fallback-not-secure-when-openssl-fails

Comment 1 Andrej Nemec 2016-05-30 11:27:13 UTC

Created php-symfony tracking bugs for this issue:

Affects: epel-6 [bug 1340831]

Comment 2 Shawn Iwinski 2016-12-28 22:02:03 UTC

All dependent bugs closed.