Vfabric Application DirectorApplication · Jenkins
CVE-2019-10419
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 vFabric Application Director Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with 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 vFabric Application Director Plugin stores user credentials in plaintext within its global configuration file on the Jenkins master file system. Any user with file system-level access to the Jenkins master can directly read these unencrypted credentials from the configuration file.
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
Vfabric Application DirectorApplication
<= 1.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Check if vFabric Application Director plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or list files in $JENKINS_HOME/plugins/ directory to see if the vfabric-application-director plugin folder existsAffected if The plugin is installed and enabled in Jenkins
-
Locate the plugin global configuration fileLook for the plugin configuration in $JENKINS_HOME/org.jenkinsci.plugins.vfabricappdirector.VfabricApplicationDirector.xml or within the main $JENKINS_HOME/config.xml under the <org.jenkinsci.plugins.vfabricappdirector> sectionAffected if A configuration file for the plugin exists on the Jenkins master
-
Inspect the configuration file for stored credentialsOpen the configuration file found in the previous step and search for any credential-related fields (such as username, password, apiKey, or similar) to see if they appear in plaintextAffected if The configuration contains visible plaintext username/password values or other credential strings that are not encrypted or masked
-
Verify credential storage methodCheck whether the credential values are stored in plain text format (visible readable characters) rather than in encrypted or masked format (such as {AQAA...} or ****)Affected if Credentials are stored as readable plaintext strings that can be directly extracted from the file
If the vFabric Application Director plugin version 1.3 or lower is installed and its configuration file contains readable plaintext credentials, the environment is affected by this CVE.
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 dataLimit filesystem access to the Jenkins master to authorized administrators only, rotate any credentials that may have been exposed, and consider migrating to Jenkins' built-in credential storage mechanisms or using a patched version of the plugin if available.
Fix this in Vfabric Application Director
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10419 — 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-10419 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