dbcve.org
Inedo BuildmasterApplication · Jenkins

CVE-2018-1999035

HIGH · 7.4 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to after 1.3 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A man in the middle vulnerability exists in Jenkins Inedo BuildMaster Plugin 1.3 and earlier in BuildMasterConfiguration.java, BuildMasterConfig.java, BuildMasterApi.java that allows attackers to impersonate any service that Jenkins connects to.

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 confidence

The Inedo BuildMaster Jenkins plugin versions 1.3 and earlier lacks proper SSL/TLS certificate validation when Jenkins connects to BuildMaster services. This MITM vulnerability allows attackers to intercept communications between Jenkins and BuildMaster, impersonate the service, and potentially inject malicious content into the build pipeline.

MitigationUpgrade the Inedo BuildMaster plugin to a version later than 1.3 which includes proper SSL/TLS certificate validation. If immediate upgrade is not possible, ensure Jenkins only connects to BuildMaster over trusted networks and consider network segmentation to reduce MITM attack surface.

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
Affected:<= 1.3

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Inedo BuildMaster plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'BuildMaster' or 'Inedo', or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i buildmaster
    Affected if The Inedo BuildMaster plugin appears in the list of installed plugins
  2. Determine the installed version of the Inedo BuildMaster plugin
    In the Manage Plugins > Installed tab, locate the Inedo BuildMaster plugin and record the version number shown in the Version column
    Affected if The version is 1.3 or earlier (versions 1.0 through 1.3 are all affected)
  3. Verify if BuildMaster integration is actively configured
    Navigate to Jenkins > Manage Jenkins > Configure System and look for the Inedo BuildMaster configuration section, or search Jenkins job configurations for BuildMaster build steps or build triggers
    Affected if A BuildMaster service URL is configured in Jenkins system settings or BuildMaster is used as a build step in any Jenkins jobs
  4. Confirm the plugin connects to a BuildMaster service
    Review the BuildMaster URL configured in Jenkins system configuration or job-level BuildMaster settings to confirm the plugin is set to communicate with a BuildMaster server
    Affected if A BuildMaster service URL is defined and the plugin will attempt to make outbound connections

The environment is affected if the Inedo BuildMaster plugin version is 1.3 or earlier AND the plugin is configured to connect to a BuildMaster service, because the missing SSL/TLS certificate validation allows MITM attacks on that communication channel.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.3
Interim mitigation

Upgrade the Inedo BuildMaster plugin to a version later than 1.3 which includes proper SSL/TLS certificate validation. If immediate upgrade is not possible, ensure Jenkins only connects to BuildMaster over trusted networks and consider network segmentation to reduce MITM attack surface.

Fix this in Inedo Buildmaster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1999035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1999035 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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