ScriptlerApplication · Jenkins
CVE-2023-50764
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 · uneditedJenkins Scriptler Plugin 342.v6a_89fd40f466 and earlier does not restrict a file name query parameter in an HTTP endpoint, allowing attackers with Scriptler/Configure permission to delete arbitrary files on the Jenkins controller file system.
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 Scriptler Plugin fails to restrict a file name query parameter in an HTTP endpoint, creating a path traversal vulnerability. Attackers with Scriptler/Configure permission can manipulate the parameter to delete arbitrary files on the Jenkins controller file system.
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
ScriptlerApplication
<= 342.v6a_89fd40f466CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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.
-
Verify Scriptler Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Scriptler', or check the plugin directory $JENKINS_HOME/plugins for a scriptler folderAffected if The Scriptler plugin is present on the Jenkins instance
-
Identify installed Scriptler versionLook at the version displayed in the plugin manager next to Scriptler, or examine the $JENKINS_HOME/plugins/scriptler/META-INF/MANIFEST.MF file for the Plugin-Version attributeAffected if The version is 342.v6a_89fd40f466 or any earlier version
-
Confirm Scriptler/Configure permission existsNavigate to Manage Jenkins > Manage and Assign Roles > Manage Roles, or check $JENKINS_HOME/config.xml for authorization strategy, then verify if any role or user has the Scriptler/Configure permission grantedAffected if Scriptler/Configure permission is assigned to users who are not fully trusted
-
Check for unauthenticated or low-privilege accessReview the overall authorization matrix at Manage Jenkins > Configure Global Security and determine if unauthenticated users or users with limited permissions can access the Scriptler endpointsAffected if Unauthenticated access is allowed or users without Scriptler/Configure permission can reach the vulnerable endpoint
You are affected if the Scriptler plugin version is 342.v6a_89fd40f466 or earlier AND Scriptler/Configure permission is granted to any user who is not fully trusted.
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.
From vendor dataUpgrade to Jenkins Scriptler Plugin version 343 or later. Until patched, restrict Scriptler/Configure permission to only trusted, authenticated users.
Fix this in Scriptler
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-50764 — 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-50764 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