Vs Team Services Continuous DeploymentApplication · Jenkins
CVE-2019-1003073
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 VS Team Services Continuous Deployment Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the 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 VS Team Services Continuous Deployment Plugin stores credentials in plain text (unencrypted) within job config.xml files on the Jenkins master. Users with Extended Read permission or direct filesystem access to the Jenkins master can view these exposed credentials in plaintext.
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
Vs Team Services Continuous DeploymentApplication
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify if the VS Team Services Continuous Deployment plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'VS Team Services Continuous Deployment' or 'tfs' in the plugin list, or check the plugin directory on the Jenkins master (typically $JENKINS_HOME/plugins/) for the tfs plugin folderAffected if The plugin appears in the installed plugins list
-
Locate job config.xml files that may use this pluginSearch the $JENKINS_HOME/jobs/ directory for config.xml files. Look for job configurations that include elements from the VS Team Services Continuous Deployment plugin, such as <tfs> or <vs-team-services> tags within the XML structureAffected if Job config.xml files contain configuration nodes associated with the plugin
-
Inspect job config.xml files for plaintext credentialsOpen the identified config.xml files and search for credential-related fields (password, username, token, password, secretKey) and examine whether the values appear as plaintext strings rather than encrypted or masked values (unencrypted credentials will appear as readable text in the XML)Affected if Credentials in the config.xml are stored as plaintext strings rather than being encrypted or masked
-
Verify Extended Read permission exposureIf the plugin is installed and jobs use it, check who has Extended Read permission (Manage Jenkins > Configure Global Security > Authorization) - any user with this permission can read job config.xml files and would be able to view the plaintext credentialsAffected if Extended Read permission is granted to users who are not fully trusted
You are affected if the VS Team Services Continuous Deployment plugin is installed and any job configurations using it contain plaintext credentials in their config.xml files.
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 to a patched version of the plugin that encrypts credentials, rotate any credentials that may have been exposed, and restrict Extended Read permission to only trusted users.
Fix this in Vs Team Services Continuous Deployment
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003073 — 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-1003073 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