# CVE-2024-5082: Nexus Repository 2 - Remote Code Execution

> Attackers can execute arbitrary code on Sonatype Nexus Repository 2 servers, requiring an upgrade to a supported version.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-6q5h-c4ff-f2vc

## What is CVE-2024-5082?

CVE-2024-5082 is a high-severity code injection vulnerability in Sonatype Nexus Repository, published on 14 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Remote Code Execution vulnerability has been discovered in Sonatype Nexus Repository 2. 

This issue affects Nexus Repository 2 OSS/Pro versions up to and including 2.15.1.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-5082?


## How do I fix CVE-2024-5082?

No fix has been published for CVE-2024-5082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5082 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5082 exists.

Public exploit code:

- Sonatype Nexus 2 - Authorized RCE POC (github_poc): https://github.com/h4mr3r/CVE-2024-5082
- Nexus Repository 2 - Remote Code Execution (nuclei): http/cves/2024/CVE-2024-5082.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5082 and fix it if it is affected.

What it is: CVE-2024-5082 is a high-severity code injection vulnerability in Sonatype Nexus Repository, published on 14 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5082 exists.

Affected product: Sonatype Nexus Repository. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5082/ (Markdown: https://insights.sbomify.com/CVE-2024-5082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5082
- OSV: https://osv.dev/vulnerability/CVE-2024-5082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5082/
Summaries are generated and may contain mistakes; the official description above is the record.