MablApplication · Jenkins
CVE-2023-37953
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 missing permission check in Jenkins mabl Plugin 0.0.46 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 mabl Plugin versions 0.0.46 and earlier lack a permission check on an endpoint, allowing any user with Overall/Read permission to connect to attacker-controlled URLs using attacker-specified credentials IDs. This enables credential theft of Jenkins-stored credentials through a server-side request forgery (SSRF)-like attack vector.
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
MablApplication
<= 0.0.46CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check if Jenkins mabl Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar get-plugins (or via /pluginManager/api/plugins JSON endpoint)Affected if The mabl plugin appears in the installed plugins list
-
Determine the installed version of the mabl PluginIn the Installed plugins tab, locate the mabl plugin and note the Version column; or query /pluginManager/api/plugins?pretty&depth=2Affected if The version number is 0.0.46 or lower (e.g., 0.0.45, 0.0.44, etc.)
-
Verify the plugin is enabled and activeCheck the Enabled status in the plugin manager, or check that the plugin appears in jenkins.model.Jenkins.getPluginManager().getPlugin("mabl")Affected if The plugin is installed and enabled (any version <= 0.0.46)
-
Confirm Overall/Read permission is granted to any usersNavigate to Manage Jenkins > Manage Users and Manage Jenkins > Configure Global Security to review which users or groups have Overall/Read accessAffected if Any user or group has Overall/Read permission enabled, allowing them to reach the vulnerable endpoint
If the mabl plugin is installed, enabled, and running version 0.0.46 or earlier while any user has Overall/Read permission, the environment is affected by this SSRF-like credential theft vulnerability.
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 the Jenkins mabl Plugin to a version newer than 0.0.46 that includes the missing permission check, and review stored credentials for potential compromise.
Fix this in Mabl
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37953 — 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-37953 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