Bug 671199 (CVE-2011-0022) - CVE-2011-0022 Directory Server: insecure pid file directory permissions
Summary: CVE-2011-0022 Directory Server: insecure pid file directory permissions
Alias: CVE-2011-0022
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
: 669767 (view as bug list)
Depends On: Red Hat670350 Embargoed670922
TreeView+ depends on / blocked
Reported: 2011-01-20 18:14 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:42 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-04-19 10:03:58 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0293 0 normal SHIPPED_LIVE Moderate: Red Hat Directory Server security update 2011-02-22 17:46:00 UTC

Description Jan Lieskovsky 2011-01-20 18:14:09 UTC
It was discovered that 389 / Red Hat Directory Server's setup scripts
set insecure permissions (0777) on the /var/run/dirsrv directory used to
store Directory Server's pid files when multiple Directory Server
instances were configured on the system to be run under the different
unprivileged users.

A local user could use this flaw to create, remove or replace pid files
in this directory, possibly preventing correct start of the Directory
Server instances, or causing Directory Server init script to kill
arbitrary process during the Directory Server shutdown.

Comment 1 Jan Lieskovsky 2011-01-20 19:29:16 UTC
The CVE identifier of CVE-2011-0022 has been assigned to this issue.

Comment 10 Dmitri Pal 2011-01-31 22:35:13 UTC
*** Bug 669767 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2011-02-22 17:46:09 UTC
This issue has been addressed in following products:

  Red Hat Directory Server 8 for RHEL 4
  Red Hat Directory Server 8 for RHEL 5

Via RHSA-2011:0293 https://rhn.redhat.com/errata/RHSA-2011-0293.html

Comment 15 Tomas Hoger 2011-04-19 10:03:58 UTC
Upstream fix:

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