IvyApplication · Jenkins
CVE-2023-41938
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Ivy Plugin 2.5 and earlier allows attackers to delete disabled modules.
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 confidenceA CSRF vulnerability in Jenkins Ivy Plugin versions 2.5 and earlier allows authenticated users to be tricked into deleting disabled modules through malicious requests. The plugin lacks proper anti-CSRF protection on the module deletion functionality.
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
IvyApplication
<= 2.5CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Jenkins Ivy Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Ivy' in the filter, or run: jenkins-cli.jar who-am-i or check $JENKINS_HOME/plugins for ivy directoryAffected if The Ivy plugin is present in the plugins directory or listed in the Jenkins plugin management interface
-
Determine the installed version of Jenkins Ivy PluginIn Jenkins UI: Manage Jenkins > Manage Plugins > Installed > Ivy Plugin - note the version number displayed. Alternatively, inspect $JENKINS_HOME/plugins/ivy/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if The version is 2.5 or lower (e.g., 2.5, 2.4, 2.3, etc.)
-
Verify if module deletion functionality existsCheck if Ivy ANT tasks or module configurations are used in Jenkins jobs. Look for Ivy-related build steps or project configurations that include module management. Access a job that uses Ivy and inspect its configuration for module-related settingsAffected if Jobs are configured with Ivy modules and the module deletion endpoint is accessible via the Jenkins API or UI (typically under job/configure or via REST API)
-
Check for CSRF protection on module deletion endpointAttempt a GET request to the module deletion API endpoint (typically /job/<job-name>/descriptorByName/ivy.IvyModuleSet/deleteModule) without a validcrumb. Also check Jenkins global security settings under Manage Jenkins > Global Security to see if CSRF protection is enabledAffected if The module deletion action completes successfully without requiring a valid Jenkinscrumb (CSRF token) in the request, or if CSRF protection is globally disabled in Jenkins security settings
You are affected if the Jenkins Ivy Plugin version is 2.5 or earlier AND module deletion functionality is accessible AND CSRF protection is not enforced on the module deletion endpoint.
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 dataUpdate Jenkins Ivy Plugin to a version that includes anti-CSRF protection (check Jenkins security advisories for the patched version). Review and test module deletion functionality after updating.
Fix this in Ivy
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41938 — 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-41938 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