Bug 1927329
| Summary: | SELinux is preventing privoxy from using the 'execmem' accesses on a process. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | chrisPL <chris_plass> |
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | dwalsh, grepl.miroslav, lvrabec, mmalik, omosnace, plautrba, vmojzis, zpytela |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:cc93a199f99d880f16fc3e5e2450ec03dac4131fa2228eeec51910ea52092045;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-10 15:14:55 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: | |||
I believe this bug is a duplicate of BZ#1917099. *** This bug has been marked as a duplicate of bug 1917099 *** |
Description of problem: Hello, It started today after my Fedora 32 workstation received a privoxy update. privoxy-3.0.31-1.fc32.x86_64 It is the first update since i upraded to F32. Latest update of selinux-policy* were done on 2021-01-20 and are at version 3.14.5-46. Thank you for you help Regards SELinux is preventing privoxy from using the 'execmem' accesses on a process. ***** Plugin allow_execmem (91.4 confidence) suggests ********************* If this issue occurred during normal system operation. Then this alert could be a serious issue and your system could be compromised. Do contact your security administrator and report this issue ***** Plugin catchall (9.59 confidence) suggests ************************** Si vous pensez que privoxy devrait être autorisé à accéder execmem sur les processus étiquetés privoxy_t par défaut. Then vous devriez rapporter ceci en tant qu'anomalie. Vous pouvez générer un module de stratégie local pour autoriser cet accès. Do autoriser cet accès pour le moment en exécutant : # ausearch -c "privoxy" --raw | audit2allow -M my-privoxy # semodule -X 300 -i my-privoxy.pp Additional Information: Source Context system_u:system_r:privoxy_t:s0 Target Context system_u:system_r:privoxy_t:s0 Target Objects Inconnu [ process ] Source privoxy Source Path privoxy Port <Inconnu> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-3.14.5-46.fc32.noarch Local Policy RPM selinux-policy-targeted-3.14.5-46.fc32.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.10.13-100.fc32.x86_64 #1 SMP Thu Feb 4 14:55:25 UTC 2021 x86_64 x86_64 Alert Count 21 First Seen 2021-02-10 15:18:32 CET Last Seen 2021-02-10 15:18:32 CET Local ID 13aaf1c7-e96c-4ce1-af3f-60e7cf7d84b1 Raw Audit Messages type=AVC msg=audit(1612966712.10:497): avc: denied { execmem } for pid=1071 comm="privoxy" scontext=system_u:system_r:privoxy_t:s0 tcontext=system_u:system_r:privoxy_t:s0 tclass=process permissive=0 Hash: privoxy,privoxy_t,privoxy_t,process,execmem Version-Release number of selected component: selinux-policy-targeted-3.14.5-46.fc32.noarch Additional info: component: selinux-policy reporter: libreport-2.13.1 hashmarkername: setroubleshoot kernel: 5.10.13-100.fc32.x86_64 type: libreport Potential duplicate: bug 1917099