CyberRota Analysis
AI-GeneratedNexus Repository 3 and its legacy version, Nexus Repository 2, are vulnerable due to improper validation of realm identifiers submitted through an internal configuration API. This flaw allows an attacker with the appropriate permissions to inject arbitrary values, potentially leading to unintended code execution and persistent authentication lockouts that are not reflected in the administrative interface. Organizations using these Nexus Repository versions, especially those managing sensitive data or critical infrastructure, should prioritize remediation to mitigate the risk of exploitation.
Original NVD Description
An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm identifiers through an internal configuration API that did not validate them against the set of registered realms. Because unrecognized entries were persisted and re-evaluated on every realm load via a legacy code path, this could result in unintended code executing inside the Nexus Repository process, and in some cases a persistent authentication lockout that was not visible through the administrative UI.