You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mridul Pathak (Jira)" <ji...@apache.org> on 2026/09/29 16:29:00 UTC
[jira] [Closed] (OFBIZ-13626) viewContentPermission() never propagates roleEntity/roleEntityField, so VIEW checks fail closed whenever a ContentPurposeOperation rule applies
[ https://issues.apache.org/jira/browse/OFBIZ-13626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mridul Pathak closed OFBIZ-13626.
---------------------------------
Fix Version/s: Upcoming Branch
24.09.08
Resolution: Fixed
> viewContentPermission() never propagates roleEntity/roleEntityField, so VIEW checks fail closed whenever a ContentPurposeOperation rule applies
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-13626
> URL: https://issues.apache.org/jira/browse/OFBIZ-13626
> Project: OFBiz
> Issue Type: Bug
> Components: content
> Affects Versions: Upcoming Branch, 24.09.07
> Reporter: Mridul Pathak
> Assignee: Mridul Pathak
> Priority: Major
> Fix For: Upcoming Branch, 24.09.08
>
>
> {{checkContentOperationSecurity()}} reads {{roleEntity}}/{{roleEntityField}} from {{parameters}} instead of its own arguments. {{createContentPermission()}} and {{updateContentPermission()}} both set those {{parameters}} keys before calling in; {{viewContentPermission()}} never does, and the field isn't even declared on {{genericContentPermission}}'s servicedef. Result: VIEW is denied for any user with {{CONTENTMGR_ROLE}} but not full {{CONTENTMGR}}, on essentially all content (via the {{_NA_}} fallback purpose). Fail-closed, not a privilege escalation. Fix: set {{parameters.roleEntity}}/{{parameters.roleEntityField}} in {{viewContentPermission()}}, mirroring {{createContentPermission()}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)