Bug 827009 - SELinux denies read access for snmpd to /var/run/net-snmp
Summary: SELinux denies read access for snmpd to /var/run/net-snmp
Status: CLOSED DUPLICATE of bug 822480
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: BaseOS QE Security Team
Depends On:
TreeView+ depends on / blocked
Reported: 2012-05-31 12:18 UTC by John Horne
Modified: 2012-05-31 13:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-05-31 13:22:16 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description John Horne 2012-05-31 12:18:11 UTC
Description of problem:
Configure snmpd to use a pass_persist program which reads data from a file in /var/run/net-snmp. The program runs as root but is denied read access to the file.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run root cron job to write to a file in /var/run/net-snmp
2. Configure /etc/snmp/snmpd.conf to run a program using the pass_persist directive which reads the above file.
3. The program will run via snmpd but is denied read access.
4. Running 'semodule -DB' will show the AVCs in /var/log/audit/audit.log
Actual results:
No output from the pass_persist program, so snmpd gives the error (in my case):
   SNMPv2-SMI::enterprises. = No Such Instance currently
   exists at this OID

Expected results:
Snmpd should have read access to anything in /var/run/net-snmp, so SNMP results should be read and returned to snmpd.

Additional info:
This was discussed on the CentOS mailing list, but has been confirmed on our RHEL 6.2 system as well:

Comment 1 John Horne 2012-05-31 12:45:05 UTC
Sorry, should have added this:

By default '/var/run/net-snmp' has the context 'system_u:object_r:var_run_t:s0'.
If I run:

   chcon -t snmpd_var_run_t /var/run/net-snmp

then the pass_persist program works fine via snmpd.

Comment 4 Miroslav Grepl 2012-05-31 13:22:16 UTC
This has been fixed.

*** This bug has been marked as a duplicate of bug 822480 ***

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