Statistics GathererApplication · Jenkins
CVE-2025-53654
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 Statistics Gatherer Plugin 2.0.3 and earlier stores the AWS Secret Key unencrypted in its global configuration file on the Jenkins controller, where it can be viewed by users with access to the Jenkins controller 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 Statistics Gatherer Plugin version 2.0.3 and earlier stores the AWS Secret Key in plaintext in its global configuration file on the Jenkins controller filesystem, enabling any user with filesystem access to view the unencrypted credential.
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
Statistics GathererApplication
<= 2.0.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
- 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 Jenkins Statistics Gatherer Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or check the $JENKINS_HOME/plugins directory for the statistics-gatherer plugin folderAffected if The plugin is present on the Jenkins controller
-
Check the installed plugin versionLook at the plugin's MANIFEST.MF file in the plugin directory, or view the version listed in the Manage Plugins interfaceAffected if The version is 2.0.3 or earlier
-
Locate the plugin global configuration fileSearch for a configuration file named statistics-gatherer.xml or similar in $JENKINS_HOME/Affected if The configuration file exists on the filesystem
-
Inspect the configuration file for AWS credentialsOpen the plugin's global configuration file and examine its contents for any AWS-related settings, specifically looking for fields named awsSecretKey, secretKey, or similarAffected if The file contains an AWS secret key stored as plaintext (not wrapped in encrypted tags)
-
Verify if credential is encryptedCheck whether the secret key value appears as raw alphanumeric string versus being enclosed within <secret> tags or other encryption markers that Jenkins uses for credentialsAffected if The secret key appears as a raw, unencrypted string value
The environment is affected if the Statistics Gatherer Plugin version 2.0.3 or earlier is installed AND the plugin's global configuration file contains an AWS Secret Key stored as plaintext without encryption.
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.
dbcve · scopedUpgrade to a patched version of the Jenkins Statistics Gatherer Plugin that properly encrypts AWS credentials, and immediately rotate any AWS secret keys that may have been exposed.
Statistics Gatherer plugin version 2.0.4 or later
- 1. Navigate to Manage Jenkins > Manage Plugins > Installed tab
- 2. Locate the 'Statistics Gatherer' plugin in the list
- 3. If an update is available, select it and click 'Update'
- 4. After update completes, restart Jenkins if required
- 5. Verify the new version is installed (should be 2.0.4 or later)
- 6. Re-enter and save the AWS Secret Key in the plugin configuration to ensure it's stored with proper encryption
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Statistics Gatherer
Scoped from the published advisory
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53654 — 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-2025-53654 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