| Summary: | SELinux is preventing sudo from using the 'setgid' capabilities. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | mrummuka <mrummuka> |
| Component: | apmd | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | dominick.grift, dwalsh, jskarvad, lvrabec, mgrepl, mrummuka, plautrba, pmoore |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:9e6f097ca64c618da585532d796690fa07c74397a38b767ba328c09de435680b;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-08 19:02:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Apmd folks, Any idea whats going on here? It's strange that somebody is still using it (it's i386 arch only). AFAIK we don't call sudo in our scripts, but user can install it's own scripts. Is it default apmd installation, or is it customized? Could you provide reproducer for this problem? Hmm. I don't have apmd installed, and I'm unaware what caused this. Could I find more information from DNF or selinux transaction history? You could check /var/log/dnf.rpm.log* to find out whether there is anything apmd related, but I am afraid, there is not much more to get from the logs. Lukas any idea? We know, there is some process with apmd label that tries to run sudo, strange and suspicious. Maybe you can also search filesystem for files with apmd SELinux labels. But it could be temporal file. Personally I would also check the system if not compromised or preventively reinstall it, but I am too paranoid ;) These are the commands that run as apmd_t. /usr/sbin/apmd -- system_u:object_r:apmd_exec_t:s0 /usr/sbin/acpid -- system_u:object_r:apmd_exec_t:s0 /usr/sbin/powersaved -- system_u:object_r:apmd_exec_t:s0 This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: SELinux is preventing sudo from using the 'setgid' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that sudo should have the setgid capability by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'sudo' --raw | audit2allow -M my-sudo # semodule -X 300 -i my-sudo.pp Additional Information: Source Context system_u:system_r:apmd_t:s0 Target Context system_u:system_r:apmd_t:s0 Target Objects Unknown [ capability ] Source sudo Source Path sudo Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.5.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.6.4-301.fc24.x86_64 #1 SMP Tue Jul 12 11:50:00 UTC 2016 x86_64 x86_64 Alert Count 86 First Seen 2016-07-28 22:22:37 EEST Last Seen 2016-07-28 22:52:36 EEST Local ID ad487ddf-643f-4afb-a39b-f42265f398d4 Raw Audit Messages type=AVC msg=audit(1469735556.119:847): avc: denied { setgid } for pid=26458 comm="sudo" capability=6 scontext=system_u:system_r:apmd_t:s0 tcontext=system_u:system_r:apmd_t:s0 tclass=capability permissive=0 Hash: sudo,apmd_t,apmd_t,capability,setgid Version-Release number of selected component: selinux-policy-3.13.1-191.5.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.9-200.fc24.x86_64 type: libreport