Call Remote JobApplication · Jenkins
CVE-2019-10422
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 Call Remote Job 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 Call Remote Job Plugin stores credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission can view these credentials through the UI, and anyone with filesystem access to the Jenkins master can read them directly from the XML files.
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
Call Remote JobApplication
<= 1.0.21CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Call Remote Job Plugin is installedNavigate to Jenkins UI: Manage Jenkins > Manage Plugins > Installed, or inspect the plugins directory: $JENKINS_HOME/plugins/ for a folder named 'call-remote-job-plugin' or similar.Affected if The plugin is present on the Jenkins instance
-
Check installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate Call Remote Job Plugin to view its version, or check the version file in $JENKINS_HOME/plugins/call-remote-job-plugin/META-INF/MANIFEST.MFAffected if Version is 1.0.21 or lower
-
Identify jobs using Call Remote Job PluginSearch job config.xml files for the presence of '<callRemoteJob>' or similar plugin-specific XML elements. Run: grep -r 'callRemoteJob' $JENKINS_HOME/jobs/*/config.xmlAffected if Any job config.xml files contain Call Remote Job Plugin configuration elements
-
Inspect for plaintext credentials in job configsOpen the config.xml files identified in the previous step and look for credential-related fields (such as passwords, API tokens, or usernames) stored in plaintext rather than masked or encrypted <credentials> elements.Affected if Plaintext credentials (visible password/token strings) are found within the Call Remote Job configuration section of any job config.xml file
-
Check Extended Read permission assignmentsIn Jenkins, go to Manage Jenkins > Manage Users > select a user, or check $JENKINS_HOME/users/ directory and review authorization settings in Configure Global Security to see which users or groups have Extended Read permission.Affected if Users other than administrators have Extended Read permission enabled
The environment is affected if Call Remote Job Plugin version 1.0.21 or lower is installed AND plaintext credentials exist in any job config.xml files using this plugin, especially if users with Extended Read permission can access those jobs.
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 from the plugin's configuration to Jenkins' built-in credential store, then remove plaintext credentials from config.xml files. Restrict Extended Read permission to prevent unauthorized credential exposure.
Fix this in Call Remote Job
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-10422 — 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-10422 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