Bugzilla – Bug 864352
VUL-0: CVE-2014-1832: rubygems-passenger: temporary file issue in Passenger rubygem
Last modified: 2016-09-08 20:26:06 UTC
CVE-2014-1832 If a local attacker can predict this filename, and precreates a symlink with the same filename that points to an arbitrary directory with mode 755, owner root and group root, then the attacker will succeed in making Phusion Passenger write files and create subdirectories inside that target directory. patch: https://github.com/phusion/passenger/commit/94428057c602da3d6d34ef75c78091066ecac5c0 References: http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-1832.html http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-1832
The SWAMPID for this issue is 56274. This issue was rated as important. Please submit fixed packages until 2014-02-25. When done, please reassign the bug to security-team@suse.de. Patchinfo will be handled by security team.
bugbot adjusting priority
Affected packages: SLE-11-SP3: rubygem-passenger SLE-11-SP2: rubygem-passenger SLE-11-SP2-PRODUCTS: rubygem-passenger
Are there any updates? The due date for submission is tomorrow, Feb. 25th. Thanks.
(In reply to comment #3) > Affected packages: > > SLE-11-SP3: rubygem-passenger > SLE-11-SP2: rubygem-passenger > SLE-11-SP2-PRODUCTS: rubygem-passenger Just a question. The call: isc maintained rubygem-passenger returns SUSE:SLE-11-SP1:Update:ATK:1.2:Update:Test/rubygem-passenger #<Project:0x00000006e7cc18>/rubygem-passenger SUSE:SLE-11-SP2:Update:Test/rubygem-passenger What about SP3 and some projects are not displayed correctly. Could you please point me to needed projects ?
(In reply to comment #4) > Are there any updates? The due date for submission is tomorrow, Feb. 25th. > > Thanks. I start today cause I have been on vacation last week. :-)
As far I see only versions of 4.0* are affected.: https://github.com/phusion/passenger/commit/94428057c602da3d6d34ef75c78091066ecac5c0 This has been a fix for version 4.0.37 or 4.0.37: https://github.com/phusion/passenger/commit/34b10878 which has been a fix for: "Affected versions: 4.0.5 and later" As long we have no package with version >=4.0 we do not need an update. Or is there any product with version 4.0.* which I have overseen ?
set need info
I have updated factory. So I think we can close it....