Bug 1235
Summary: | There has been a security exploit reported against LSOF | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Siebenmann <cks-rhbugzilla> |
Component: | lsof | Assignee: | David Lawrence <dkl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | cks-rhbugzilla |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-02-19 16:04:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Siebenmann
1999-02-18 23:27:09 UTC
/dev/kmem under Linux is read-only, so it is not vulnerable to a root compromise. It's not clear to me if read access to kmem (apparently obtainable through the lsof exploit on RedHat 5.2, since lsof is setgid kmem and /dev/kmem is group-readable for kmem) can be used to do evil things. RedHat might want to look into the situation and make a statement one way or another. (Or it might be simpler and less time consuming to just release new lsof RPMs built from 4.40 + Vic's patch.) The immediate fix is chmod g-s /usr/sbin/lsof An updated errata of lsof-4.40 with Vic Abel's patch will be issued shortly. |