Fortify CloudscanApplication · Jenkins
CVE-2018-1000607
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 · uneditedA arbitrary file write vulnerability exists in Jenkins Fortify CloudScan Plugin 1.5.1 and earlier in ArchiveUtil.java that allows attackers able to control rulepack zip file contents to overwrite any file on the Jenkins master file system, only limited by the permissions of the user the Jenkins master process is running as.
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 Fortify CloudScan Plugin versions 1.5.1 and earlier contain an arbitrary file write vulnerability in ArchiveUtil.java. Attackers who can control rulepack zip file contents can write to arbitrary files on the Jenkins master filesystem, limited only by the permissions of the user the Jenkins master process runs as.
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
Fortify CloudscanApplication
<= 1.5.1CVSS 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.0/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 Fortify CloudScan plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins/fortify-cloudscan directory existsAffected if The plugin directory exists and contains the Fortify CloudScan plugin files
-
Check the installed plugin versionOpen the plugin manifest at $JENKINS_HOME/plugins/fortify-cloudscan/META-INF/MANIFEST.MF and look for the Implementation-Version attribute, or view the version in the Jenkins plugin manager UIAffected if The version is 1.5.1 or earlier (e.g., 1.5.1, 1.5.0, 1.4.x, etc.)
-
Identify if rulepack upload functionality is accessibleCheck Jenkins job configurations and Fortify CloudScan plugin settings for any rulepack upload, import, or modification options; inspect any freestyle or pipeline jobs using the Fortify CloudScan pluginAffected if Users with job configuration or plugin configuration permissions can upload or modify rulepack ZIP files
-
Review user permissions for plugin configurationNavigate to Manage Jenkins > Manage Users and check who has Overall/Administer, Job/Configure, or credentials permissions that allow access to rulepack upload featuresAffected if Users other than trusted administrators can configure rulepack settings or upload rulepack files
You are affected if the Fortify CloudScan plugin version is 1.5.1 or earlier AND untrusted users have access to configure or upload rulepack ZIP files through Jenkins jobs or plugin configuration.
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 Fortify CloudScan Plugin to a version newer than 1.5.1 that contains the security fix, and restrict access to rulepack upload/modification functionality to trusted users only.
Fix this in Fortify Cloudscan
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000607 — 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-2018-1000607 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