Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1412678 - (CVE-2016-2339) CVE-2016-2339 ruby: Fiddle::Function.new heap buffer overflow
CVE-2016-2339 ruby: Fiddle::Function.new heap buffer overflow
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20160614,repor...
: Security
Depends On:
Blocks: 1412685
  Show dependency treegraph
 
Reported: 2017-01-12 09:35 EST by Andrej Nemec
Modified: 2017-01-18 08:01 EST (History)
24 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-17 19:19:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-01-12 09:35:15 EST
An exploitable heap overflow vulnerability exists in the Fiddle::Function.new “initialize” function functionality of Ruby. In Fiddle::Function.new “initialize” heap buffer “arg_types” allocation is made based on args array length. Specially constructed object passed as element of args array can increase this array size after mentioned allocation and cause heap overflow.

References:

http://www.talosintelligence.com/reports/TALOS-2016-0034/
Comment 2 Doran Moppert 2017-01-17 19:07:42 EST
This flaw requires executing untrusted ruby code, or passing an untrusted class to the Fiddle module.  Either of these would already represent a vulnerability by design, so the impact from this flaw is Moderate at best.

The Fiddle module is not present in Ruby prior to version 1.9, so earlier versions are not affected.
Comment 3 Doran Moppert 2017-01-17 19:20:21 EST
Statement:

Red Hat Product Security has rated this issue as having Moderate security
impact. This issue is not currently planned to be addressed in future
updates. For additional information, refer to the Issue Severity
Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.