Zephyr Enterprise Test ManagementApplication · Jenkins
CVE-2019-1003085
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 missing permission check in Jenkins Zephyr Enterprise Test Management Plugin in the ZeeDescriptor#doTestConnection form validation method allows attackers with Overall/Read permission to initiate a connection to an attacker-specified server.
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 confidenceA missing permission check in the Zephyr Enterprise Test Management Plugin allows users with only Overall/Read permission to trigger the doTestConnection form validation method, enabling them to initiate connections to arbitrary servers controlled by the attacker. This creates a Server-Side Request Forgery (SSRF) vulnerability where authenticated users can make the Jenkins server connect to internal or external systems.
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.6CVSS 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.1/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 if Zephyr Enterprise Test Management Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Zephyr Enterprise Test Management' or 'zephyr' in the plugin listAffected if The plugin appears in the installed plugins list
-
Confirm the installed plugin versionIn the Installed plugins tab, locate the Zephyr Enterprise Test Management plugin and note the Version columnAffected if The version number is 1.6 or lower
-
Check for the doTestConnection endpoint exposureAttempt to access the form validation endpoint for test connections - typically found in the plugin's configuration page under the test connection button, or via direct URL if the plugin exposes REST endpointsAffected if The test connection form can be triggered or submitted without elevated permissions
-
Verify user permission configurationReview Jenkins user permissions by checking Manage Jenkins > Manage Users and reviewing Overall/Read permission assignments in Configure Global SecurityAffected if Users with only Overall/Read permission can access the plugin's connection test functionality
If the Zephyr Enterprise Test Management Plugin version 1.6 or lower is installed AND users with Overall/Read permission can access the doTestConnection form validation, 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 Zephyr Enterprise Test Management Plugin to the patched version. If no patch is available, consider removing or disabling the plugin until a fix is released. Alternatively, restrict Overall/Read access to trusted users only.
Fix this in Zephyr Enterprise Test Management
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003085 — 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-1003085 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