Nexus PlatformApplication · Jenkins
CVE-2023-50767
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing permission checks in Jenkins Nexus Platform Plugin 3.18.0-03 and earlier allow attackers with Overall/Read permission to send an HTTP request to an attacker-specified URL and parse the response as XML.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Nexus Platform Plugin versions 3.18.0-03 and earlier lack proper permission checks on an endpoint, allowing any authenticated user with only Overall/Read permission to send HTTP requests to attacker-specified URLs and parse the resulting XML response. This is a Server-Side Request Forgery (SSRF) vulnerability combined with unsafe XML parsing, enabling potential internal network probing and XML-based attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nexus PlatformApplication
<= 3.18.0-03CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Nexus Platform Plugin is installedGo to Manage Jenkins > Manage Plugins > Installed tab and search for 'Nexus Platform', or check the $JENKINS_HOME/plugins directory for a nexus-platform folderAffected if The plugin is present in Jenkins
-
Check the installed version of Nexus Platform PluginView the plugin details in the Installed Plugins UI, or inspect the manifest file at $JENKINS_HOME/plugins/nexus-platform/META-INF/MANIFEST.MFAffected if Version is 3.18.0-03 or earlier (the version number matches or is lower than the affected range)
-
Confirm users with Overall/Read permission existNavigate to Manage Jenkins > Configure Global Security and review the authorization matrix, or check if the security realm allows any authenticated user to have Overall/Read permissionAffected if There are users or groups with only Overall/Read permission (this permission is often granted by default to authenticated users in standard security configurations)
Your environment is affected if the Nexus Platform Plugin version is 3.18.0-03 or earlier AND your Jenkins instance permits any authenticated user to have Overall/Read permission, as this combination allows the SSRF and unsafe XML parsing vulnerability to be exploited.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the Nexus Platform Plugin to a version later than 3.18.0-03, which includes proper permission validation. If immediate patching is not feasible, restrict Overall/Read permissions and limit network connectivity from the Jenkins controller.
3.18.0-04 or later
- 1. In Jenkins, go to Manage Jenkins > Manage Plugins
- 2. Click on the 'Installed' tab
- 3. Find 'Nexus Platform Plugin' in the list
- 4. If an update is available, click 'Update now' or install version 3.18.0-04 or later
- 5. Restart Jenkins if required
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nexus Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50767 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data