Bug 1300643 - keyutils command line parsing error causes out of bounds memory read
Summary: keyutils command line parsing error causes out of bounds memory read
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: keyutils
Version: 7.4
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: David Howells
QA Contact: Kun Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-21 10:49 UTC by hanno
Modified: 2020-12-15 07:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:39:46 UTC
Target Upstream Version:


Attachments (Terms of Use)
[patch] fix command line parsing (404 bytes, text/plain)
2016-01-21 10:49 UTC, hanno
no flags Details

Description hanno 2016-01-21 10:49:23 UTC
Created attachment 1116893 [details]
[patch] fix command line parsing

I noticed an out of bounds read access in keyctl when compiling it with
address sanitizer (add -fsanitize=address to cflags).

I figured out it was the code for parsing the command line, here:
        for (cmd = commands; cmd->name; cmd++) {
                if (!cmd->action)
                        continue;
                if (strlen(cmd->name) > n)
                        continue;
                if (memcmp(cmd->name, *argv, n) != 0)
                        continue;

The strlen(cmd->name) > n comparison seems wrong, it must be <. Because
when the cmd->name is shorter than argv there never can be a partial
match, if it is larger then there can be. This error causes the memcmp
command to read invalid memory.

(I reported this a while back directly to the maintainer via email, but received no reply. The last release of keyutils was in 2014.)

Comment 2 hanno 2017-05-27 19:02:31 UTC
I noted that a new release of keyutils was published recently, yet this bug is still in there.
It's a pretty obvious bug and a straightforward fix, so I wonder: why?

Comment 3 Stanislav Zidek 2017-05-31 10:12:20 UTC
Hi,

this bug is for RHEL-7 and keyutils were not ever updated there. If you require fix in RHEL-7, you need to contact the regular Red Hat support channels to request it.

What I would suggest is to pursue the fix in fedora/upstream first. Let me know if there is anything I can help you with.

Comment 4 hanno 2018-02-04 17:45:19 UTC
Hi, I actually wanted to report this upstream. This tool is hosted on a redhat webpage [1], so my assumption is this is upstream. Who else should I report it?

[1] https://people.redhat.com/dhowells/keyutils/

Comment 6 RHEL Program Management 2020-12-15 07:39:46 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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