dbcve.org
SitemonitorApplication · Jenkins

CVE-2019-10317

MEDIUM · 5.9 CVSS v3.0 Published 2019-04-30
Fix available
A fix is available. Upgrade to after 0.5 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Jenkins SiteMonitor Plugin 0.5 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM.

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 SiteMonitor Plugin version 0.5 and earlier disabled SSL/TLS certificate and hostname verification globally for the entire Jenkins master JVM, not just for its own connections. This means all outbound HTTPS communications from Jenkins lost security validation, making the system vulnerable to man-in-the-middle attacks.

MitigationUpdate the SiteMonitor plugin to a version newer than 0.5 that does not disable SSL/TLS verification, or remove the plugin if not needed. Review all outbound HTTPS connections and consider credential rotation as a precaution due to potential exposure.

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
SitemonitorApplication
Affected:<= 0.5

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
None
Availability
None

CVSS:3.0/AV:N/AC:H/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 checks

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

  1. Verify SiteMonitor plugin is installed
    List installed plugins in Jenkins via the web UI (Manage Jenkins > Manage Plugins > Installed) or via the Jenkins CLI/API
    Affected if The SiteMonitor plugin appears in the list of installed plugins
  2. Check SiteMonitor plugin version
    View the details of the SiteMonitor plugin in the installed plugins list to confirm the exact version number
    Affected if The installed version is 0.5 or any version lower than 0.5
  3. Identify globally disabled SSL verification
    Examine the SiteMonitor plugin configuration or source code for settings that disable SSL/TLS certificate and hostname verification (such asTrustManager or HostnameVerifier configurations set to accept all)
    Affected if SSL/TLS verification is explicitly disabled or set to accept all certificates/hosts in the plugin configuration or code

A user is affected if the SiteMonitor plugin version 0.5 or earlier is installed and it contains configuration that disables SSL/TLS verification globally for the Jenkins JVM

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.5
Interim mitigation

Update the SiteMonitor plugin to a version newer than 0.5 that does not disable SSL/TLS verification, or remove the plugin if not needed. Review all outbound HTTPS connections and consider credential rotation as a precaution due to potential exposure.

Fix this in Sitemonitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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