Date: September 1, 2021
Nexus Repository 3 versions up to and including 3.33.1
Fixed in Version:
Nexus Repository 3 version 3.34.0 and later
Medium - 6.5 - (CVSS3.1:AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N)
We have discovered an HTTP Header Injection vulnerability in Nexus Repository 3.
Sonatype Nexus Repository 3.x through 3.33.1-01 is vulnerable to an HTTP header injection. By sending a specially crafted HTTP request, a remote attacker may disclose sensitive information or request external resources from the vulnerable instance. This advisory provides the pertinent information needed to properly address this vulnerability along with details on how to reach us if you have any further questions or concerns.
We are highly recommending that you upgrade all instances of Nexus Repository 3 to 3.34.0 or later. You can download the latest Nexus Repository 3 version from the following location:
For detailed information on upgrading, please see the following:
Upgrading Nexus Repository 3.1.0 and Newer
If you run into any problems or have any questions/concerns, please contact us by filing a ticket at https://support.sonatype.com.
Sonatype thanks NVADR Research (firstname.lastname@example.org, https://redhuntlabs.com/) for finding and reporting this issue.
Frequently Asked Questions:
Q: What is the risk associated with this vulnerability?
A: An unauthenticated attacker may disclose sensitive information or request external resources from the vulnerable instance.
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 submit a malicious request.
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 that absolutely required in order to assess the 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 and an effort to achieve the most rapid remediation possible.