360 FirelineApplication · Jenkins
CVE-2022-43435
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 360 FireLine Plugin 1.7.2 and earlier programmatically disables Content-Security-Policy protection for user-generated content in workspaces, archived artifacts, etc. that Jenkins offers for download.
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 360 FireLine Plugin versions 1.7.2 and earlier contains functionality that programmatically disables Content-Security-Policy (CSP) protection headers that Jenkins normally applies to user-generated content. This affects content served from workspaces and archived artifacts, potentially allowing injection of malicious scripts or content into downloads.
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
360 FirelineApplication
<= 1.7.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify if the 360 FireLine plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or list the contents of $JENKINS_HOME/plugins/ directory, and look for a plugin named '360 FireLine' or 'fireline'Affected if The 360 FireLine plugin appears in the installed plugin list
-
Check the installed version of the 360 FireLine pluginIn the Jenkins UI at Manage Jenkins > Manage Plugins > Installed, locate the 360 FireLine plugin and note the version number displayedAffected if The installed version is 1.7.2 or any version lower than 1.7.2
-
Confirm CSP headers are disabled for workspace contentUse the Jenkins Script Console to run: Jenkins.instance.getItemByFullName('your-job').builds.each { println it.absoluteUrl } and inspect HTTP response headers on workspace URLs, or use a browser DevTools Network tab to check Content-Security-Policy header on a workspace file URLAffected if The Content-Security-Policy header is missing or blank on workspace URLs when the plugin is installed and enabled
-
Confirm CSP headers are disabled for archived artifactsNavigate to a job that has archived artifacts, click on an archived file, and inspect the HTTP response headers using browser DevTools or curl -I to check for the presence of the Content-Security-Policy headerAffected if The Content-Security-Policy header is missing or blank on archived artifact URLs when the plugin is installed and enabled
You are affected if the 360 FireLine plugin version 1.7.2 or earlier is installed AND your Jenkins instance serves workspace or archived artifact content without CSP headers.
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 dataUpdate the 360 FireLine Plugin to a version newer than 1.7.2 that removes the CSP-disabling functionality, or uninstall the plugin if not required.
Fix this in 360 Fireline
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43435 — 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-2022-43435 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