Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1414304 - (CVE-2017-0386) CVE-2017-0386 libnl: Privilege escalation due to insufficient data checks in nla_reserve and nla_put
CVE-2017-0386 libnl: Privilege escalation due to insufficient data checks in ...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20161201,reported=2...
: Security
Depends On: 1414305
Blocks: 1414309
  Show dependency treegraph
 
Reported: 2017-01-18 04:32 EST by Andrej Nemec
Modified: 2017-01-19 07:56 EST (History)
7 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-18 20:11:46 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-18 04:32:58 EST
An elevation of privilege vulnerability in the libnl library could enable a
local malicious application to execute arbitrary code within the context of a
privileged process.

References:

https://android.googlesource.com/platform/external/libnl/+/f0b40192efd1af977564ed6335d42a8bbdaf650a
https://github.com/thom311/libnl/issues/124
Comment 1 Andrej Nemec 2017-01-18 04:33:24 EST
Created libnl3 tracking bugs for this issue:

Affects: fedora-all [bug 1414305]
Comment 2 Doran Moppert 2017-01-18 20:05:07 EST
This CVE seems to be specific to Android's usage of (its fork of) libnl, allowing calls into libnl to cross process (and therefore privilege) boundaries.

On Fedora and Enterprise Linux, libnl inherits the privilege domain of the process which opens it (through dynamic linking or dlopen()) .. like any other shared library.  Thus, this does not represent a security vulnerability.

The same conclusion has been reached on the upstream ticket:

https://github.com/thom311/libnl/issues/124

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