StarteamApplication · Jenkins
CVE-2019-10277
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 StarTeam 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 StarTeam Plugin stores credentials in plain text within job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem access to the Jenkins master can view these unencrypted 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
StarteamApplication
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.
-
Verify StarTeam Plugin is installedCheck the Jenkins plugin directory ($JENKINS_HOME/plugins/) for the starteam plugin folder, or use the Jenkins web UI: Manage Jenkins > Manage Plugins > Installed, search for StarTeam.Affected if The StarTeam plugin appears in the installed plugins list
-
Identify jobs using StarTeamSearch job config.xml files for 'starteam' or 'StarTeam' entries. In the Jenkins home directory, examine each $JENKINS_HOME/jobs/<jobname>/config.xml file and look for StarTeam-related configuration sections.Affected if Any job's config.xml contains StarTeam configuration blocks
-
Check credential storage format in config.xmlOpen the config.xml files of jobs that use StarTeam. Look for <password>, <credentials>, or similar credential fields within the StarTeam section. Determine whether the value appears as plain text (readable characters) or as an encrypted/obfuscated string.Affected if Credential fields in the StarTeam section of config.xml contain plain text passwords rather than encrypted values
-
Verify Extended Read access existsCheck Jenkins matrix-based security or folder-based permissions. Go to Manage Jenkins > Configure Global Security > Authorization. Determine if any users or groups have Extended Read permission enabled.Affected if Extended Read permission is granted to any user or group beyond administrators
If the StarTeam plugin is installed AND any job config.xml files contain readable plain text passwords in StarTeam configuration sections, the environment is affected by this credential exposure 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 dataUpgrade to a patched version of the StarTeam Plugin and rotate all credentials that may have been exposed. Restrict Extended Read permissions and ensure job config.xml files are not accessible to unauthorized users.
Fix this in Starteam
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10277 — 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-10277 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