Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 584196 (CVE-2016-7091) - sys-libs/readline: Possible info leak via INPUTRC (CVE-2016-7091)
Summary: sys-libs/readline: Possible info leak via INPUTRC (CVE-2016-7091)
Status: RESOLVED FIXED
Alias: CVE-2016-7091
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Security
URL: https://lists.gnu.org/archive/html/bu...
Whiteboard: A4 [upstream]
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-26 12:08 UTC by Agostino Sarubbo
Modified: 2020-05-25 16:37 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2016-05-26 12:08:12 UTC
From ${URL} :

It was found that malicious user can leak some information about arbitrary files by providing 
arbitrary value for INPUTRC, since the target application parses the INPUTRC file with the target 
user's privileges. This kind of attack is in current version of readline limited to only timing 
attacks and leaks of line content matching a very particular format. It is also possible to cause 
segmentation fault in the target application by having INPUTRC specify a file with an $include 
directive for itself.

Upstream bug:

https://lists.gnu.org/archive/html/bug-readline/2016-05/msg00009.html


@maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
Comment 1 Christopher Díaz Riveros (RETIRED) gentoo-dev Security 2017-07-20 13:05:06 UTC
Update from See Also [1]:

CVE Assignment: (CVE-2016-7091)

http://seclists.org/oss-sec/2016/q3/376
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2020-05-25 16:37:46 UTC
I don't think our sudo config ever had INPUTRC in env_keep. The segfault is also not reproducible anymore.

As per the oss-security message, it's not really clare if this was ever a proper vulnerability, or that it affected us. Thanks to ajak for checking this out.