dbcve.org
MablApplication · Jenkins

CVE-2023-37952

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 0.0.46 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins mabl Plugin 0.0.46 and earlier allows attackers 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 · moderate confidence

This is a CSRF vulnerability in Jenkins mabl Plugin version 0.0.46 and earlier that allows authenticated users to be tricked into making unintended requests. An attacker can exploit this by luring a user to visit a malicious page, causing the user's browser to send authenticated requests to connect to an attacker-specified URL using attacker-specified Jenkins credential IDs. The attacker can capture the credentials that Jenkins retrieves, leading to credential exfiltration.

MitigationUpgrade the Jenkins mabl Plugin to a version newer than 0.0.46 when available. Until then, restrict access to the affected plugin's functionality and monitor for unauthorized credential access.

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
Affected:<= 0.0.46

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify mabl Plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'mabl' in the plugin list, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i mabl
    Affected if The mabl plugin appears in the installed plugins list
  2. Check installed mabl Plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find the mabl Plugin, and note the version number displayed. Alternatively, check the $JENKINS_HOME/plugins directory for the mabl plugin folder and read its manifest or version file.
    Affected if The installed version is 0.0.46 or earlier
  3. Verify mabl integration is configured
    Go to Jenkins > Manage Jenkins > Configure System and look for the mabl configuration section. Check if any mabl integrations, API keys, or credentials are configured there.
    Affected if mabl integration settings are present and configured with credentials
  4. Inspect configured credentials
    Go to Jenkins > Manage Jenkins > Manage Credentials and review any credentials with 'mabl' in the description or associated with mabl-related jobs or configurations.
    Affected if There are Jenkins credentials configured for mabl integration
  5. Review recent job configurations for mabl usage
    Check Jenkins jobs that use mabl functionality. Look at job configuration pages for any mabl-related build steps or post-build actions, particularly those that may reference external URLs or credential IDs.
    Affected if Jobs are configured to use mabl plugin features that could trigger the CSRF-vulnerable endpoints

A user is affected if the mabl Plugin version 0.0.46 or earlier is installed AND the plugin is configured with credentials or integrated into Jenkins jobs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 0.0.46
Interim mitigation

Upgrade the Jenkins mabl Plugin to a version newer than 0.0.46 when available. Until then, restrict access to the affected plugin's functionality and monitor for unauthorized credential access.

Fix this in Mabl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37952 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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