Insufficient granularity of access control for Remote Connector Servers in client mode
An insufficient granularity of access control vulnerability exists in PingIDM (formerly ForgeRock Identity Management) where administrators cannot properly configure access rules for Remote Connector Servers (RCS) running in client mode. This means attackers can spoof a client-mode RCS (if one exists) to intercept and/or modify an identity’s security-relevant properties, such as passwords and account recovery information. This issue is exploitable only when an RCS is configured to run in client mode.
Description: CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs
Solutions
Both of the following steps are required to mitigate the issue:
* Upgrade to one of the fixed versions listed previously.
* Secure the /openicf endpoint using the new access and authentication configuration options (refer to migration dependent features https://docs.pingidentity.com/pingoneaic/latest/product-information/migration-dependent-features.html#current_migration_dependent_features for more details).
Configurations
At least one RCS configured in client mode in PingIDM
Workarounds
Configure a reverse proxy (such as PingGateway) to enforce IP and certificate-based rules to the /openicf endpoint.
Configure all RCS instances to run in server mode.