Sonatype Nexus Repository 3 Security Advisory
Date: August 11th, 2020
Affected Versions: All previous Nexus Repository 3 OSS/Pro versions up to and including 3.25.1
Fixed in Version: Nexus Repository OSS/Pro version 3.26.0
Risk: Medium - 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N)
An access controls bypass vulnerability (CVE-2020-15868) has been discovered in Nexus Repository 3.
An unauthenticated user can craft requests in such a manner that intended access controls are bypassed in some cases. We have fixed the issue so that the affected content cannot be accessed without proper authentication and authorization. This advisory provides the pertinent information needed to properly address this vulnerability, along with the details on how to reach us if you have any further questions or concerns.
This vulnerability was identified by an external researcher and has been verified by our security team. We are not aware of any active exploits taking advantage of this issue. However, we strongly encourage all users of Nexus Repository 3 to immediately take the steps outlined in this advisory.
We are highly recommending all instances of Nexus Repository be upgraded to version 3.26.0 or later.
For detailed information on upgrade, please see:
Sonatype thanks firstname.lastname@example.org from Dbappsecurity Co., Ltd for responsibly reporting the identified issue and working with us as we addressed it.
If you run into any problems or have any questions/concerns, please contact us by filing a ticket at https://support.sonatype.com.
Frequently Asked Questions:
Q: What is the risk associated with this vulnerability?
A: An attacker can craft specific requests that will allow the user to view some content they are not authorized to view.
Q: What preconditions must be met in order to be vulnerable?
A: An attacker must have network access to the Nexus Repository instance in order to view protected content such as configuration files. Therefore, internet-accessible instances imply available access by a very large audience versus the more limited audience associated with non-internet-accessible instances
Q: Are there implications associated with this advisory itself?
A: Disclosure unfortunately means bad actors may try to take advantage. While we have initially limited the information to the minimum details necessary for users to affect an appropriate fix, this merely slows down a would-be attacker. As such, we are advising all organizations utilizing Nexus Repository to immediately assess their individual impact and take appropriate action in response.
Q: Where can I obtain more information associated with the vulnerability?
A: At this time, and in the interest of best protecting our user community, we are limiting the information released to what absolutely required in order to assess impact and affect remediation. Please contact support for more information.
Q: Why is Sonatype making this information available?
A: This is part of a responsible disclosure process. Given Nexus Repository is an open-source project with over 150,000 active server installations, notifying the user base will invariably lead to broad dissemination. We are taking a concerted and proactive approach in our outreach activities in an effort to achieve the most rapid remediation possible.