Mathworks PolyspaceApplication · Jenkins
CVE-2023-37960
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 MathWorks Polyspace Plugin 1.0.5 and earlier allows attackers with Item/Configure permission to send emails with arbitrary files from the Jenkins controller file systems.
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 MathWorks Polyspace Plugin for Jenkins versions 1.0.5 and earlier contains a path traversal vulnerability in its email functionality. An attacker with Item/Configure permission can abuse the plugin to attach and send arbitrary files from the Jenkins controller file system via email, leading to sensitive data exfiltration.
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
Mathworks PolyspaceApplication
<= 1.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Verify MathWorks Polyspace Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'MathWorks Polyspace' or 'polyspace' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Manage Plugins > Installed section, locate the MathWorks Polyspace Plugin and note the version number displayedAffected if Version is 1.0.5 or earlier
-
Confirm email feature is configuredNavigate to a job configured with the MathWorks Polyspace Plugin and inspect whether email notifications are enabled in the build configurationAffected if Email notifications are enabled and the plugin is used in job configurations
-
Review Item/Configure permission scopeNavigate to Manage Jenkins > Manage Users and check which users or groups have the Item/Configure or Job/Configure permission, typically found in matrix authorization or project-based authorization settingsAffected if Users beyond trusted administrators have Item/Configure permission enabled
Your environment is affected if the MathWorks Polyspace Plugin version 1.0.5 or earlier is installed with the email feature in use and users with Item/Configure permission exist beyond trusted administrators.
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.
dbcve · scopedUpgrade the MathWorks Polyspace Plugin to version 1.0.6 or later. Until then, restrict the Item/Configure permission to trusted users only and monitor for suspicious email activity.
MathWorks Polyspace Plugin > 1.0.5 (latest available version on Jenkins plugin repository)
- Check Jenkins plugin repository (plugins.jetbrains.io) for the latest MathWorks Polyspace Plugin version
- Upgrade the MathWorks Polyspace Plugin to the latest available version through Jenkins Plugin Manager
- Restart Jenkins to apply the plugin update
- Verify the plugin version has been updated in Manage Plugins > Installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mathworks Polyspace
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37960 — 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-37960 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