Squash Tm PublisherApplication · Jenkins
CVE-2021-43578
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 Squash TM Publisher (Squash4Jenkins) Plugin 1.0.0 and earlier implements an agent-to-controller message that does not implement any validation of its input, allowing attackers able to control agent processes to replace arbitrary files on the Jenkins controller file system with an attacker-controlled JSON string.
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 Squash TM Publisher plugin (Squash4Jenkins) version 1.0.0 and earlier contains an agent-to-controller message handler that lacks any input validation. Attackers who compromise or control agent processes can send specially crafted messages to cause the controller to overwrite arbitrary files on the Jenkins controller filesystem with attacker-supplied JSON content.
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
Squash Tm PublisherApplication
<= 1.0.0CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Squash TM Publisher plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Squash TM Publisher' or 'Squash4Jenkins'. Check the version column.Affected if The plugin is installed and version is 1.0.0 or earlier.
-
Confirm Jenkins agents are configuredGo to Manage Jenkins > Manage Nodes. Review the list of configured agents (including clouds and permanent agents).Affected if Any agent is configured and connected, as the vulnerability requires agent-to-controller message handling.
-
Inspect plugin configuration for Squash TM PublisherGo to Manage Jenkins > Configure System and look for 'Squash TM Publisher' or 'Squash4Jenkins' configuration sections. Check if any test execution settings are defined.Affected if The plugin is actively configured with test result publishing settings.
-
Review recent controller filesystem changesExamine Jenkins logs (Manage Jenkins > System Log) for any file write operations or errors related to the Squash TM Publisher. Check workspace and userContent directories for unexpected JSON files.Affected if Unexpected JSON files appear in Jenkins directories or logs show file write errors from agent messages.
You are affected if the Squash TM Publisher plugin is installed at version 1.0.0 or earlier and any Jenkins agents (even configured but untrusted ones) can communicate with the controller.
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 to a patched version of the Squash4Jenkins plugin when available. In the interim, restrict agent access, monitor agent-to-controller communications, and ensure agents are running on trusted infrastructure.
Fix this in Squash Tm Publisher
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43578 — 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-2021-43578 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