dbcve.org
Eagle TesterApplication · Jenkins

CVE-2020-2129

MEDIUM · 6.5 CVSS v3.1 Published 2020-02-12
Fix available
A fix is available. Upgrade to after 1.0.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Jenkins Eagle Tester Plugin 1.0.9 and earlier stores a password unencrypted in its global configuration file on the Jenkins master where it 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 confidence

The Jenkins Eagle Tester Plugin versions 1.0.9 and earlier stores passwords in plaintext within its global configuration file on the Jenkins master node. Users with file system access to the Jenkins master can read these unencrypted passwords directly from the configuration file.

MitigationUpdate to a patched version of the Eagle Tester Plugin that implements proper password encryption. Alternatively, ensure strict file system access controls on the Jenkins master and rotate any credentials that may have been exposed.

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
Eagle TesterApplication
Affected:<= 1.0.9

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Eagle Tester plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Eagle Tester' in the list, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | findstr -i eagle
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    In the Manage Plugins > Installed tab, locate the Eagle Tester plugin and note the Version column. Alternatively, examine the plugin's .jpi file in $JENKINS_HOME/plugins/ for the version manifest
    Affected if The version is 1.0.9 or earlier (e.g., 1.0.9, 1.0.8, 1.0.7, etc.)
  3. Locate the plugin's global configuration file
    Navigate to $JENKINS_HOME (the Jenkins home directory) and look for the Eagle Tester configuration file. Common naming patterns include 'eagle-tester.xml', 'hudson.plugins.eagletester.EagleTesterPlugin.xml', or similar XML files in the root of JENKINS_HOME
    Affected if The configuration file exists in the Jenkins home directory
  4. Inspect configuration file for plaintext passwords
    Open the Eagle Tester configuration file using a text editor or run: cat $JENKINS_HOME/[config-filename] | grep -i password. Look for XML elements containing password values in plaintext (not encrypted/hashed)
    Affected if Password fields contain visible plaintext strings rather than encrypted values (e.g., <password>mysecretpass</password> instead of <password>encrypted:abc123...</password>)
  5. Verify credentials are actually configured
    Navigate to Jenkins > Manage Jenkins > Configure System > Eagle Tester section (or similar configuration page for the plugin). Check if any password fields have been populated and saved
    Affected if Credentials/passwords have been entered and saved in the plugin configuration

A user is affected if the Eagle Tester plugin version is 1.0.9 or earlier AND the plugin's global configuration file contains plaintext (unencrypted) passwords.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.9
Interim mitigation

Update to a patched version of the Eagle Tester Plugin that implements proper password encryption. Alternatively, ensure strict file system access controls on the Jenkins master and rotate any credentials that may have been exposed.

Fix this in Eagle Tester Scoped from the published advisory
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2129 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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