Zephyr Enterprise Test ManagementApplication · Jenkins
CVE-2019-1003084
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 cross-site request forgery vulnerability in Jenkins Zephyr Enterprise Test Management Plugin in the ZeeDescriptor#doTestConnection form validation method allows attackers 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 confidenceCSRF vulnerability in Jenkins Zephyr Enterprise Test Management Plugin's ZeeDescriptor#doTestConnection form validation method allows attackers to trick authenticated users into initiating connections to attacker-controlled servers via malicious web pages.
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
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm Zephyr Enterprise Test Management Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Zephyr Enterprise' or 'Zephyr' in the plugin listAffected if The plugin appears in the installed plugins list
-
Verify the plugin versionIn the Installed plugins tab, locate the Zephyr Enterprise Test Management Plugin and note its version number. Compare this version against any available patch information from Jenkins security advisoriesAffected if Any version is present, as all versions of this plugin are affected according to the CVE
-
Confirm the ZeeDescriptor form validation endpoint existsAccess the plugin configuration page at Jenkins > Manage Jenkins > Configure System > Zephyr Enterprise configuration, locate the 'Test Connection' or similar form validation buttonAffected if The form validation functionality is accessible without any CSRF crumb being required or validated
-
Check for CSRF protection on form validationInspect the HTTP response or use browser developer tools to observe whether a Jenkins CSRF crumb token (crumb parameter) is required when submitting the test connection formAffected if The form submission succeeds without requiring or validating a CSRF crumb token
If the Zephyr Enterprise Test Management Plugin is installed and its Test Connection form validation endpoint can be accessed without proper CSRF crumb validation, the environment is affected by this vulnerability.
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 a patched version that includes CSRF protection (crumb validation) in the form validation endpoint. Ensure Jenkins global CSRF protection is enabled as an additional defense layer.
Fix this in Zephyr Enterprise Test Management
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-2019-1003084 — 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-1003084 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