11.1.1 Hotfix Release Notes

July 3rd, 2021:

Privilege Manager v11.1.1 is a hotfix release to resolve issues discovered in v11.0.0 and v11.1.0 instance and agent deployments.

Bug Fixes

  • Parameter Name for Import Azure Users/Groups task is incorrect.
  • Indexes missing or duplicated for resource key items.
  • Computer Group Based on Azure AD Security Group Not Showing Correct Machines.
  • The Group Member Authentication Action is unable to resolve Azure AD groups to allow authentication.
  • The Import Specific Azure AD Users and Groups task does not resolve correctly against the specified user or group name.
  • The Justify Action message in policies errors out and does not allow a user to run an application as intended by the policy.

Agents

  • Improvements for agent database file locations.

Security

  • Removal of account name information from GET method for CreateItemByRoleType.

Known Issues

  • There is a security issue with Windows Core agent versions 13.0.1058 and older. A fix for this issue is included in v12 versions 12.0.5804 and newer, and v13 versions 13.0.2064 and newer of the Windows Core agent which is available on the Software Downloads page.

    Delinea recommends customers who cannot immediately upgrade to use group policy or device management tooling to take the following actions on their workstations running the Privilege Manager Windows agent:

    This workaround covers remote connections. For coverage against a local connection, upgrading the Window Core agent is required.

    • Privilege Manager Cloud: Block inbound TCP on port 5593. There is no degradation in function from blocking the port.

    • Privilege Manager On-premises: Block inbound TCP on port 5593, or at least restrict it to your Privilege Managerr web server IP address. If you block the port, agents pull updates from the server based on a set schedule.

  • When a Justification Message action is triggered by an application control policy for an application process that is started via commandline, the agent creates an error. The workaround is, to exclude admins from the justification request and to use a policy with an Advanced Message Action.