Team Foundation ServerApplication · Jenkins
CVE-2021-21637
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 Foundation Server Plugin 5.157.1 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 confidenceA missing permission check in Jenkins Team Foundation Server Plugin 5.157.1 and earlier allows attackers with Overall/Read permission to connect to attacker-specified URLs using attacker-specified credentials IDs obtained through another method, enabling capture of credentials stored in Jenkins.
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 Foundation ServerApplication
<= 5.157.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
- 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 Foundation Server Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Team Foundation Server' or 'TFS' in the list of installed pluginsAffected if Plugin is not present in the installed plugins list, then not affected
-
Check installed TFS plugin versionIn the Installed plugins list, locate the Team Foundation Server Plugin and note the Version column. Compare this version number to 5.157.1Affected if Version is 5.157.1 or lower, meaning the plugin is within the affected version range
-
Verify plugin is configured with credentialsNavigate to Manage Jenkins > Configure System and look for 'Team Foundation Server' or 'TFS' configuration section. Check if any credentials are configured or referenced for TFS connectionsAffected if The plugin has credential configurations defined, which could be exploited through the missing permission check
-
Check for unusual TFS endpoint configurationsIn the TFS plugin configuration, review any configured server URLs, repository paths, or credential IDs. Look for unfamiliar or unexpected URLs that could indicate attempted exploitationAffected if Configurations contain unexpected or attacker-specified URLs that were not intentionally set by administrators
The environment is affected if the Team Foundation Server Plugin is installed at version 5.157.1 or earlier and has credential configurations, as the missing permission check allows any user with Overall/Read access to potentially access those credentials.
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 Jenkins Team Foundation Server Plugin to version 5.157.2 or later which includes proper permission checks to prevent unauthorized credential access.
Fix this in Team Foundation Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21637 — 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-2021-21637 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