Inedo BuildmasterApplication · Jenkins
CVE-2019-10411
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 Inedo BuildMaster Plugin 2.4.0 and earlier transmitted configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure.
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 Inedo BuildMaster Jenkins plugin versions 2.4.0 and earlier transmitted configured credentials in plain text as part of the global Jenkins configuration form, allowing exposure of sensitive authentication credentials to anyone with access to the configuration page.
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
Inedo BuildmasterApplication
<= 2.4.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 BuildMaster plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'BuildMaster' or 'Inedo', or inspect the $JENKINS_HOME/plugins/ directory for a buildmaster folder.Affected if The BuildMaster plugin folder exists in the Jenkins plugins directory.
-
Determine installed plugin versionIn Jenkins UI, locate BuildMaster in the Installed Plugins list and note the Version column, or read the Version attribute from $JENKINS_HOME/plugins/buildmaster/META-INF/MANIFEST.MFAffected if The reported version is 2.4.0 or earlier.
-
Check if BuildMaster credentials are configuredNavigate to Jenkins > Manage Jenkins > Configure System and locate the BuildMaster settings section. Verify whether any credentials (API key, username, password, or access token) have been configured in the BuildMaster configuration form.Affected if Credentials fields in the BuildMaster configuration section contain values.
-
Inspect credential transmission in configuration formView the page source or use browser developer tools to examine the HTML form submitted when saving the global Jenkins configuration. Look for input fields containing plain text credential values in the BuildMaster configuration section.Affected if The BuildMaster credentials appear as plain text values in the HTML form rather than being masked or encrypted.
The environment is affected if the BuildMaster plugin version is 2.4.0 or earlier AND credentials have been configured in the BuildMaster global configuration, as these credentials would be transmitted in plain text.
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 Inedo BuildMaster plugin to a version newer than 2.4.0 and rotate any credentials that may have been transmitted or stored in plain text.
Fix this in Inedo Buildmaster
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10411 — 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-10411 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