Wildfly DeployerApplication · Jenkins
CVE-2019-1003072
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 WildFly Deployer 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 WildFly Deployer Plugin stores credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission (a lenient permission in Jenkins that allows viewing job configurations without full configuration access) or anyone with file system access to the Jenkins master can view these credentials in cleartext, 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
Wildfly DeployerApplication
all versionsCVSS 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 WildFly Deployer plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'WildFly Deployer', or run: ls $JENKINS_HOME/plugins/ | grep -i wildflyAffected if Plugin is listed as installed
-
Identify jobs using WildFly DeployerSearch job config.xml files for 'wildfly-deployer' or 'wildfly' related configuration elements. Run: find $JENKINS_HOME/jobs -name config.xml -exec grep -l -i wildfly {} \;Affected if Any jobs reference WildFly Deployer plugin configuration
-
Inspect job config.xml for plaintext credentialsExamine the config.xml files of identified jobs. Look for username, password, or credential-related fields in cleartext within the WildFly Deployer configuration sectionAffected if Credentials appear as plaintext values in the config.xml
-
Check if Extended Read permission is broadly grantedNavigate to Manage Jenkins > Manage and Assign Roles > Check if Extended Read is granted to users or groups who do not need full job configuration accessAffected if Extended Read permission is granted to users beyond administrators
If the WildFly Deployer plugin is installed and jobs using it contain plaintext credentials in their config.xml files, the environment is affected by this vulnerability.
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 dataRestrict or revoke Extended Read permission from users who do not require full job configuration access, rotate any exposed credentials immediately, and migrate to Jenkins credential binding mechanisms (such as Credentials Binding plugin) which properly encrypt stored credentials.
Fix this in Wildfly Deployer
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003072 — 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-1003072 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