Caliper CiApplication · Jenkins
CVE-2019-10351
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 · uneditedJenkins Caliper CI Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
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 confidenceThe Jenkins Caliper CI Plugin stores credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem access to the Jenkins master can view these unencrypted credentials, leading to credential 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
Caliper CiApplication
<= 2.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Caliper CI plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or inspect the $JENKINS_HOME/plugins directory for a folder named 'caliper-ci' or similar Caliper plugin filesAffected if The plugin is present in the plugins directory or listed as installed
-
Check plugin version against affected rangeInspect the plugin's manifest file (META-INF/MANIFEST.MF) or view the plugin details in the Jenkins plugin manager to determine the installed version numberAffected if The installed version is 2.3 or lower
-
Identify jobs using Caliper pluginSearch job config.xml files (in $JENKINS_HOME/jobs/*/config.xml) for '<caliper-ci>' or '<caliper>' configuration blocks, or search for 'caliper' related credentials sectionsAffected if Any job configuration files contain Caliper plugin configuration elements
-
Inspect for plaintext credentials in job configsOpen the identified job config.xml files and search within the Caliper configuration blocks for credential fields. Check if username/password or API tokens appear as plaintext values rather than <credentials> or <secret> references to Jenkins credential storeAffected if Credentials are stored as visible plaintext values (not masked or referencing Jenkins credential bindings)
-
Review Extended Read permission scopeCheck Jenkins authorization matrix or matrix-based security settings at Manage Jenkins > Configure Global Security, and review individual job configurations for which users or groups have Extended Read permissionAffected if Users other than administrators have Extended Read permission, especially on jobs with Caliper configurations
The environment is affected if the Caliper CI plugin version 2.3 or lower is installed and any job configuration files contain plaintext credentials within Caliper settings.
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 dataMigrate credentials to Jenkins' built-in credential binding mechanism or encrypted secret storage, rotate any exposed credentials, and restrict Extended Read permission to only trusted users.
Fix this in Caliper Ci
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10351 — 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-10351 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