Official Owasp ZapApplication · Jenkins
CVE-2019-1003060
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 Official OWASP ZAP Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master 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 confidenceThe Jenkins Official OWASP ZAP Plugin stores credentials in plaintext within its global configuration file on the Jenkins master filesystem. Any user with access to the master file system can view these unencrypted credentials, leading to credential exposure.
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
Official Owasp ZapApplication
all versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if OWASP ZAP plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'OWASP ZAP' or 'Official OWASP Zap'. Alternatively, check the plugin directory at $JENKINS_HOME/plugins for a folder named 'owasp-zap' or 'official-owasp-zap'.Affected if The plugin is present in the installed plugins list or filesystem.
-
Locate the plugin configuration fileFind the global configuration file for the OWASP ZAP plugin. This is typically stored at $JENKINS_HOME/org.jenkinsci.plugins.owasp.ZAP.global.xml or within the Jenkins configuration files related to the plugin.Affected if A configuration XML file for the plugin exists on the Jenkins master filesystem.
-
Inspect configuration for plaintext credentialsOpen the configuration file identified in the previous step using a text editor or run a command like 'cat $JENKINS_HOME/org.jenkinsci.plugins.owasp.ZAP.global.xml' to view its contents. Look for fields containing username, password, or API key values that appear as plain, unencrypted text.Affected if Credentials such as passwords or API keys are stored as plaintext (not wrapped in <mask> tags or otherwise encrypted) within the configuration file.
-
Verify file system access to the configurationCheck file permissions on the configuration file by running 'ls -la' on the file path. Verify which system users and Jenkins users have read access to the file.Affected if The configuration file is readable by users other than the Jenkins process owner, or accessible through the Jenkins file system.
If the OWASP ZAP plugin is installed and its configuration file contains plaintext credentials accessible on the filesystem, the environment is affected by this CVE.
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 plugin to a version that encrypts credentials, and rotate any exposed credentials. Restrict filesystem access to the Jenkins master and leverage Jenkins' built-in credential storage mechanisms.
Fix this in Official Owasp Zap
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003060 — 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-2019-1003060 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