Team ConcertApplication · Jenkins
CVE-2019-16566
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 Team Concert Plugin 1.3.0 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 Team Concert Plugin for Jenkins versions 1.3.0 and earlier lacks proper permission checks, allowing any user with basic Overall/Read permission to enumerate credential IDs and use them to connect to attacker-controlled URLs, thereby exfiltrating stored Jenkins 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
Team ConcertApplication
<= 1.3.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 Team Concert Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Team Concert' or 'Jazz' related plugins, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName.contains('team-concert') || it.displayName.contains('Team Concert')) { println "Found: ${it.displayName} version ${it.version}" } }Affected if The Team Concert plugin is present in the Jenkins instance
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate the Team Concert plugin and verify the version number in the 'Version' columnAffected if The installed version is 1.3.0 or earlier
-
Identify if credentials are configured for the pluginNavigate to Manage Jenkins > Manage Credentials and review any credentials scoped to Jenkins or specific projects that may be used by the Team Concert plugin, or query via script console: Jenkins.instance.credentialsStore.domainCredentials.each { println it.credentials.collect { it.id } }Affected if Any credentials are configured in Jenkins that could be accessed by the plugin
-
Check for users with Overall/Read permissionNavigate to Manage Jenkins > Manage Users or check authorization matrix in Manage Jenkins > Configure Global Security to see which users or groups have Overall/Read accessAffected if Any user accounts exist with Overall/Read permission (this is default in most Jenkins installations)
If the Team Concert plugin version is 1.3.0 or earlier AND credentials are configured in Jenkins AND users with Overall/Read permission exist, the environment is vulnerable to credential enumeration and exfiltration via 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 dataUpgrade the Team Concert Plugin to version 1.3.1 or later which includes proper permission checks, and review credential storage and usage policies in Jenkins.
Fix this in Team Concert
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16566 — 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-16566 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