Title

MarkLogic Server must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. (Cat II impact)

Discussion

Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. System documentation should include a definition of the functionality considered privileged. Depending on circumstances, privileged functions can include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. A privileged function in the DBMS/database context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to: CREATE ALTER DROP GRANT REVOKE DENY There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples include: TRUNCATE TABLE; DELETE, or DELETE affecting more than n rows, for some n, or DELETE without a WHERE clause; UPDATE or UPDATE affecting more than n rows, for some n, or UPDATE without a WHERE clause; any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal. Depending on the capabilities of the DBMS and the design of the database and associated applications, the prevention of unauthorized use of privileged functions may be achieved by means of DBMS security features, database triggers, other mechanisms, or a combination of these.

Check Content

Review the MarkLogic system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question. Review MarkLogic users and assigned roles 1. Navigate to the MarkLogic Admin page >> Security >> Roles. 2. Validate user-created roles have appropriate permissions/roles applied. 3. Navigate to the MarkLogic Admin page >> Security >> Users. 4. Verify user-created Users are only granted roles meeting their specific requirements and do not allow for unnecessary elevated privileges. If Users are assigned roles providing unnecessary elevated or privileged permissions, this is a finding. If Roles are defined with unnecessary elevated permissions, this is a finding.

Fix Text

Review MarkLogic User and Role configurations to ensure correct privileges are assigned and update as required. 1. Navigate to the MarkLogic Admin page >> Security >> Roles. 2. Select specific roles (usually custom defined roles by administrator) and only apply privileges with the least amount of permissions required for a given role. 3. Navigate to the MarkLogic Admin Page >> Security >> Users. 4. Select specific users (usually custom defined users by an administrator) and add/remove roles allowing for the least amount of privileges required for the specified user. 5. Save configuration and repeat for each user-defined User/Role.

Additional Identifiers

Rule ID: SV-220377r879717_rule

Vulnerability ID: V-220377

Group Title: SRG-APP-000340-DB-000304

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.