Aws Device FarmApplication · Jenkins
CVE-2019-1003064
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 aws-device-farm 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 aws-device-farm Plugin stores AWS credentials unencrypted in its global configuration file on the Jenkins master filesystem. Users with access to the master file system can read these plaintext credentials.
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
Aws Device FarmApplication
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.
-
Check if Aws Device Farm plugin is installedGo to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'aws-device-farm' or 'AWS Device Farm', or use the Jenkins CLI: jenkins-cli.jar who-am-i or check /var/jenkins_home/plugins directory for aws-device-farm.*.jpi filesAffected if The plugin is installed and enabled in Jenkins
-
Locate the plugin's global configuration fileOn the Jenkins master filesystem, navigate to the Jenkins home directory (commonly /var/jenkins_home or C:\Program Files\Jenkins) and find the aws-device-farm.xml configuration file, typically located in the Jenkins home root or in a subdirectoryAffected if The configuration file exists on the Jenkins master filesystem
-
Inspect the configuration file for plaintext credentialsRead the contents of the aws-device-farm.xml file using a text editor, cat command, or file viewer. Look for AWS access key IDs and secret access keys stored as plain text values within the XML structureAffected if The configuration file contains plaintext AWS credentials (accessKeyId or secretAccessKey values visible in clear text)
-
Verify filesystem permissions on the configuration fileCheck file permissions on aws-device-farm.xml using 'ls -la' (Linux/Unix) or right-click > Properties > Security (Windows). Verify which users and groups have read access to this fileAffected if The file is readable by users other than the Jenkins administrator account
A user is affected if the Aws Device Farm plugin is installed and the aws-device-farm.xml configuration file contains unencrypted AWS credentials accessible to unauthorized users.
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 stored credentials to Jenkins' built-in credential store or ensure filesystem permissions are restricted to only authorized administrators. Remove any plaintext credentials from the configuration file.
Fix this in Aws Device Farm
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003064 — 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-1003064 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