Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Release Branch 4.0, Release Branch 09.04, Trunk, Upcoming Branch
-
None
-
None
-
Bug Crush Event - 21/2/2015
Description
This issue was first brought up here: https://sourceforge.net/forum/message.php?msg_id=7496877
Basically, any user with PARTYMGR_CREATE/UPDATE permissions can set the password of another user. This creates opportunity for Malfeasance. For example, a customer service rep could set the password of the admin user.
A simple solution would be to create a new security permission PARTYMGR_PASSWD and require that permission for setting or changing password of a different user, instead of using PARTYMGR_UPDATE. PARTYMGR_PASSWD could then be associated with the administrative user.
An alternative is to use the SECURITY_UPDATE permission instead of PARTYMGR_UPDATE or a new PARTYMGR_PASSWD permission.
Attachments
Issue Links
- is part of
-
OFBIZ-1868 Move Security-Related UI Artifacts to the Common Component
- Closed