dbcve.org
Inedo ProgetApplication · Jenkins

CVE-2018-1999034

HIGH · 7.4 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to after 0.8 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 ProGet Plugin 0.8 and earlier in ProGetApi.java, ProGetConfig.java, ProGetConfiguration.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 Jenkins Inedo ProGet Plugin versions 0.8 and earlier lacks proper SSL/TLS certificate validation when connecting to ProGet servers. This allows man-in-the-middle attackers to intercept and impersonate the ProGet service that Jenkins communicates with, potentially injecting malicious content or stealing credentials.

MitigationUpgrade the Inedo ProGet Plugin to a version beyond 0.8 that properly validates SSL certificates when establishing connections to ProGet servers.

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 ProgetApplication
Affected:<= 0.8

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. Verify Inedo ProGet Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and search for 'ProGet' or 'Inedo', or inspect the plugin directory $JENKINS_HOME/plugins/ for a folder named 'proget' or 'inedo-proget'
    Affected if The plugin folder exists in the Jenkins plugins directory
  2. Determine the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the Inedo ProGet entry to view its version number, or read the META-INF/MANIFEST.MF file inside the plugin folder
    Affected if The reported version is 0.8 or earlier
  3. Check for configured ProGet server connection
    Navigate to Manage Jenkins > Configure System and look for the ProGet or Inedo ProGet configuration section; verify if a ProGet server URL is specified in the 'ProGet Server URL' or similar field
    Affected if A ProGet server URL is configured and the plugin is actively communicating with it

You are affected if the Inedo ProGet Plugin version is 0.8 or earlier AND a ProGet server URL is configured in Jenkins, enabling insecure SSL/TLS connections to that server.

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 0.8
Interim mitigation

Upgrade the Inedo ProGet Plugin to a version beyond 0.8 that properly validates SSL certificates when establishing connections to ProGet servers.

Fix this in Inedo Proget Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1999034 — 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-1999034 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