dbcve.org
MatlabApplication · Jenkins

CVE-2023-49655

HIGH · 8.8 CVSS v3.1 Published 2023-11-29
Fix available
A fix is available. Upgrade to 2.11.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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 MATLAB Plugin 2.11.0 and earlier allows attackers to have Jenkins parse an XML file from 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 confidence

This is a CSRF vulnerability in the Jenkins MATLAB Plugin versions 2.11.0 and earlier. Attackers can exploit this to trick authenticated Jenkins users into triggering requests that cause the Jenkins controller to parse arbitrary XML files from its local file system. This could potentially lead to XML External Entity (XXE) attacks or sensitive file disclosure depending on the XML content.

MitigationUpdate Jenkins MATLAB Plugin to a version beyond 2.11.0 (once available) to obtain the CSRF protection fix. Until then, minimize exposure by restricting Jenkins user permissions and monitoring for suspicious requests.

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
MatlabApplication
Affected:< 2.11.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checks

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

  1. Verify Jenkins MATLAB Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: jenkins-cli.jar groovy = println(Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'matlab' })
    Affected if The plugin is not listed in installed plugins, then you are not affected by this vulnerability.
  2. Check the installed MATLAB Plugin version
    In the Installed plugins tab, locate the MATLAB Plugin and note the version number. Or check the plugin's manifest file: $JENKINS_HOME/plugins/matlab/META-INF/MANIFEST.MF
    Affected if The installed version is 2.11.0 or earlier. Versions prior to 2.11.1 are vulnerable.
  3. Identify if any MATLAB build steps or configurations accept XML file inputs
    Review Jenkins job configurations that use the MATLAB Plugin. Look for build steps that reference XML files, particularly in MATLAB Builder or MATLAB Compiler configurations.
    Affected if Jobs are configured to parse or process XML files through the MATLAB Plugin, which could be triggered via CSRF to read arbitrary local files.
  4. Check current CSRF protection settings
    Navigate to Manage Jenkins > Configure Global Security and verify if CSRF protection is enabled. The plugin vulnerability exists regardless of global CSRF settings, but confirmation helps assess exposure.
    Affected if CSRF protection is disabled, increasing the exploitability of this vulnerability.
  5. Review user permissions for MATLAB Plugin jobs
    Check which users or groups have permission to configure or run jobs that use the MATLAB Plugin, via Manage Jenkins > Manage Users and job-level permissions.
    Affected if Users with lower privilege levels can access MATLAB Plugin jobs, allowing them to potentially trigger the XML parsing via CSRF.

You are affected if the Jenkins MATLAB Plugin is installed with version 2.11.0 or earlier, and your environment allows authenticated users to access jobs that could be manipulated to parse arbitrary XML files from the Jenkins controller's file system.

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.

dbcve · scoped
Upgrade available Upgrade to 2.11.1 or later
Fixed in 2.11.1
Interim mitigation

Update Jenkins MATLAB Plugin to a version beyond 2.11.0 (once available) to obtain the CSRF protection fix. Until then, minimize exposure by restricting Jenkins user permissions and monitoring for suspicious requests.

Recommended fix Moderate confidence

Jenkins MATLAB Plugin version 2.11.1

  1. 1. Identify the Jenkins controller running the MATLAB Plugin
  2. 2. Navigate to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab to view installed plugins
  4. 4. Locate the 'MATLAB' plugin in the list
  5. 5. If the installed version is 2.11.0 or earlier, select the plugin and click 'Update'
  6. 6. Alternatively, manually download the updated .hpi file from the Jenkins plugin repository (https://plugins.jenkins.io/matlab/)
  7. 7. Restart Jenkins to apply the update
  8. 8. Verify the plugin version shows 2.11.1 or later under Manage Plugins > Installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Matlab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49655 — 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-49655 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