Zephyr Enterprise Test ManagementApplication · Jenkins
CVE-2020-2145
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 Zephyr Enterprise Test Management Plugin 1.9.1 and earlier stores its Zephyr password in plain text on the Jenkins 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 Zephyr Enterprise Test Management Plugin version 1.9.1 and earlier stores the Zephyr server password in plain text within configuration files on the Jenkins master file system. Any user with file system access to the Jenkins controller can read the stored credentials.
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
Zephyr Enterprise Test ManagementApplication
<= 1.9.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 Zephyr Enterprise Test Management Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins directory for a folder named 'zephyr-enterprise-test-management' or similarAffected if The plugin is present in the Jenkins environment
-
Determine the installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate Zephyr Enterprise Test Management Plugin to read the version number. Alternatively, check the version file inside the plugin folder: $JENKINS_HOME/plugins/zephyr-enterprise-test-management/META-INF/MANIFEST.MFAffected if The installed version is 1.9.1 or earlier
-
Locate Zephyr plugin configuration filesSearch for configuration files containing 'zephyr' in $JENKINS_HOME, particularly in $JENKINS_HOME/org.jenkinsci.plugins.zephyr_enterprise_test_management (or similar path under $JENKINS_HOME/config.xml or the plugin's config.xml)Affected if Configuration files for the Zephyr plugin exist on the Jenkins controller
-
Inspect configuration files for plaintext credentialsOpen the Zephyr plugin configuration files identified in the previous step and search for password fields. Look for plain text strings that appear to be passwords, especially in XML elements named 'password', 'secret', 'credentials', or similarAffected if The configuration files contain plaintext Zephyr server passwords rather than encrypted or masked values
-
Check file permissions on configuration filesUse file system commands (ls -la) to examine read permissions on the Zephyr plugin configuration files in $JENKINS_HOMEAffected if Configuration files containing Zephyr credentials are readable by users other than the Jenkins service account
The environment is affected if the Zephyr Enterprise Test Management Plugin version 1.9.1 or earlier is installed and configuration files containing plaintext Zephyr server passwords exist and are accessible.
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 the Zephyr Enterprise Test Management Plugin to version 1.9.2 or later where passwords are properly encrypted. Rotate any exposed Zephyr credentials as a precaution and verify file permissions on Jenkins configuration directories.
Fix this in Zephyr Enterprise Test Management
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2145 — 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-2020-2145 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