Static Analysis UtilitiesApplication · Jenkins
CVE-2019-10307
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 · uneditedA cross-site request forgery vulnerability in Jenkins Static Analysis Utilities Plugin 1.95 and earlier in the DefaultGraphConfigurationView#doSave form handler method allowed attackers to change the per-job default graph configuration for all users.
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 confidenceCross-site request forgery (CSRF) vulnerability in Jenkins Static Analysis Utilities Plugin 1.95 and earlier. The DefaultGraphConfigurationView#doSave form handler lacked proper CSRF protection, allowing attackers to craft malicious requests that could change per-job default graph configuration settings for all users through tricking authenticated Jenkins users into visiting attacker-controlled pages.
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
Static Analysis UtilitiesApplication
<= 1.95CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Jenkins Static Analysis Utilities plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Static Analysis Utilities', or inspect the $JENKINS_HOME/plugins/ directory for a file named static-analysis-utils.hpi or similarAffected if The plugin is not present in the installed plugins list or plugins directory
-
Determine the installed version of the pluginIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed, find Static Analysis Utilities, and note the version number displayed. Alternatively, examine the plugin manifest.xml file within the plugin archiveAffected if The reported version is 1.95 or any version lower than 1.96 (such as 1.94, 1.93, etc.)
-
Verify the DefaultGraphConfigurationView component is accessibleThe vulnerability affects the DefaultGraphConfigurationView#doSave form handler used for per-job graph configuration. Check if users have access to job configuration pages that include graph configuration settings under the Static Analysis plugin sectionsAffected if Users can access job configuration pages with graph configuration options and the form submission lacks a validcrumb or CSRF token in the request
If the Static Analysis Utilities plugin is installed at version 1.95 or earlier, the environment is affected by this CSRF vulnerability in the DefaultGraphConfigurationView form handler.
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 Jenkins Static Analysis Utilities Plugin to version 1.96 or later which contains the CSRF protection fix. As a general precaution, users should avoid browsing untrusted sites while authenticated to Jenkins.
Fix this in Static Analysis Utilities
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10307 — 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-10307 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