Sonatype Nexus Security Advisory
Date: Oct 17, 2024
Affected Versions: All previous Sonatype Nexus Repository Manager 3.x OSS/Pro versions up to and including 3.72.0
Fixed in Version: Sonatype Nexus Repository OSS/Pro version 3.73.0
Summary:
A vulnerability has been discovered in Nexus Repository 3 requiring immediate action. The vulnerability was present in the code responsible for encrypting any secrets stored in the Nexus Repository configuration database (SMTP or HTTP proxy credentials, user tokens, tokens, among others). The previous code relied on a static hard-coded encryption passphrase. While it was possible for an administrator to define an alternate encryption passphrase, it could only be done at first boot and not updated.
We have mitigated the issue with a new product capability. This mechanism allows you to configure an encryption passphrase, rotate it with a new value, and re-encrypt any stored secrets.
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.
Recommendation:
We are highly recommending all affected instances of Sonatype Nexus Repository 3 be upgraded to Nexus Repository version 3.73.0 or later. Download the latest version from the following location:
https://help.sonatype.com/en/download.html
Immediate Mitigation Options:
Upgrading Nexus Repository is the recommended approach for eliminating this vulnerability.
Once upgraded, follow the instructions provided at https://help.sonatype.com/en/re-encryption-in-nexus-repository.html for setting a new passphrase and re-encrypting stored secrets.
Credit:
This issue was discovered and reported responsibly by Dylan Evans at/of Maveris, LLC via Sonatype’s Bug Bounty Program.
Support:
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: If an attacker is able to access the internal database of the Nexus Repository deployment and the secrets are encrypted only with the default static hard-coded encryption passphrase, those secrets will be trivially reversible.
Q: What preconditions must be met in order to be vulnerable?
A: Any Nexus Repository 3 deployment running 3.72.0 or earlier is vulnerable.
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 using 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 that 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. We are taking a concerted and proactive approach in our outreach activities in an effort to achieve the most rapid remediation possible for our customers and users.