Aqua Security ScannerApplication · Jenkins
CVE-2019-10428
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 Aqua Security Scanner Plugin 3.0.17 and earlier transmitted configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure.
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 Aqua Security Scanner Plugin versions 3.0.17 and earlier transmitted stored credentials in plain text as part of the global configuration form submission. This exposes credentials in transit and potentially in logs, compromising confidentiality.
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
Aqua Security ScannerApplication
<= 3.0.17CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Aqua Security Scanner Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i aquaAffected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn the Installed Plugins tab, locate 'Aqua Security Scanner' and note the version number displayedAffected if Version is 3.0.17 or lower
-
Check if credentials are configured in the pluginNavigate to Jenkins > Manage Jenkins > Configure System, locate the 'Aqua Security Scanner' section, and verify if any credentials are saved in the Global Credentials fieldsAffected if Credentials fields contain saved values (the plain text transmission only occurs when credentials are actually configured)
-
Review Jenkins logs for plain text credentialsExamine Jenkins logs (typically in $JENKINS_HOME/logs) or servlet container logs for the string patterns matching the configured credential values, which may appear in plain text during configuration savesAffected if Plain text credential values appear in logs (indicating past exploitation or exposure)
You are affected if the Aqua Security Scanner Plugin version is 3.0.17 or lower AND credentials have been saved in the plugin's global configuration, as this combination triggers plain text transmission of credentials during form submission.
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 a patched version of the Aqua Security Scanner Plugin. Rotate all credentials that were configured in the affected plugin as they may have been exposed.
Fix this in Aqua Security Scanner
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-10428 — 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-10428 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