Statistics GathererApplication · Jenkins
CVE-2025-53655
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 does not mask the AWS Secret Key on the global configuration form, increasing the potential for attackers to observe and capture it.
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 2.0.3 and earlier fails to mask the AWS Secret Key field on its global configuration page, displaying the credential in plain text. This allows attackers with screen access or browser-based observation to capture the secret key.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Statistics Gatherer plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Statistics Gatherer', or use the CLI: jenkins-plugin-cli --plugins statistics-gatherer:2.0.3Affected if plugin is present in the installed plugins list
-
Check installed plugin versionOn the Installed Plugins page, locate the Statistics Gatherer plugin and note the version number displayed in the Version columnAffected if version is 2.0.3 or earlier (versions prior to 2.0.4)
-
Verify AWS credentials are configuredNavigate to Jenkins > Manage Jenkins > Configure System and look for the Statistics Gatherer section. Check if an AWS Access Key ID and AWS Secret Access Key are populated in the configuration fieldsAffected if AWS Secret Access Key field contains a value (even if masked)
-
Confirm secret key visibility vulnerabilityIn the Statistics Gatherer AWS configuration section, examine the AWS Secret Access Key input field. The field should display masked characters (dots or asterisks) but this vulnerability causes it to display in plain textAffected if AWS Secret Access Key field displays the actual credential characters instead of masking them
Environment is affected if Statistics Gatherer plugin version 2.0.3 or earlier is installed AND AWS Secret Access Key is configured, with the secret visible in plain text on the configuration page.
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 dataUpdate to plugin version 2.0.4 or later which masks the AWS Secret Key field. As a precautionary measure, rotate any AWS secret keys that may have been exposed through this vulnerability.
Fix this in Statistics Gatherer
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53655 — 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-53655 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