Static Analysis UtilitiesApplication · Jenkins
CVE-2019-10308
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 missing permission check in Jenkins Static Analysis Utilities Plugin 1.95 and earlier in the DefaultGraphConfigurationView#doSave form handler method allowed attackers with Overall/Read permission 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 confidenceMissing permission check in Jenkins Static Analysis Utilities Plugin allows attackers with Overall/Read permission to modify the per-job default graph configuration for all users via the DefaultGraphConfigurationView#doSave form handler method.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Verify Static Analysis Utilities plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Static Analysis Utilities' or check the plugin directory $JENKINS_HOME/plugins for the static-analysis-utilities folderAffected if The plugin is present in the Jenkins environment
-
Determine the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the Static Analysis Utilities plugin and read the Version column; alternatively, check the version file in $JENKINS_HOME/plugins/static-analysis-utilities/META-INF/MANIFEST.MFAffected if The version number is 1.95 or lower
-
Check user permissions on the systemNavigate to Jenkins > Manage Jenkins > Manage Users and review which users have Overall/Read permission, particularly any users who should NOT have configuration modification accessAffected if Users with Overall/Read permission exist who should not have ability to modify global settings
-
Verify access to DefaultGraphConfigurationView doSave endpointAttempt to access or check the URL pattern /descriptorByName/DefaultGraphConfigurationView/doSave or review any accessible job configuration forms that invoke this endpointAffected if The doSave form handler method is accessible to users with only Overall/Read permission
If the Static Analysis Utilities plugin version is 1.95 or lower and users with only Overall/Read permission can access the DefaultGraphConfigurationView doSave method, the environment is vulnerable to CVE-2019-10308.
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 Jenkins Static Analysis Utilities Plugin to version 1.96 or later which implements proper permission validation in the doSave method.
Fix this in Static Analysis Utilities
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10308 — 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-10308 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