Nexus Repository - Arbitrary Class Instantiation via Unsafe Realm Configuration
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Nexus Repository 3.95.0.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Sonatype | Nexus Repository | >=2.8.0 <3.95.0 | 3.95.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Nexus Repository, strongest first
Embed
A live severity badge for an advisory, README or ticket