Aqua Security ScannerApplication · Jenkins
CVE-2019-1003069
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 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 Aqua Security Scanner Plugin stores credentials in plaintext within its global configuration file on the Jenkins master. Users with access to the master file system can directly read these unencrypted 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
Aqua Security ScannerApplication
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 Aqua Security Scanner plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or list the contents of $JENKINS_HOME/plugins/ directory and look for 'aqua-security-scanner' or 'aqua' folder.Affected if The plugin folder exists in $JENKINS_HOME/plugins/ or the plugin appears in the installed plugins list.
-
Locate the plugin configuration fileLook for configuration files in $JENKINS_HOME/plugins/aqua-security-scanner/ directory, or search for config.xml files containing 'aqua' or 'aqua-security-scanner' references within $JENKINS_HOME/.Affected if A config.xml file associated with the Aqua Security Scanner plugin exists.
-
Inspect configuration file for plaintext credentialsOpen the identified configuration file (typically config.xml in the plugin directory or within the main Jenkins config.xml) using a text editor or grep command and look for credential fields such as 'username', 'password', 'secretKey', or 'apiToken'.Affected if The configuration contains unencrypted credential strings (plaintext passwords, API keys, or secrets) rather than encrypted or hashed values.
-
Verify credential storage formatCheck if the credential values appear as raw plaintext strings rather than in encrypted format (Jenkins credentials plugin typically stores encrypted credentials as long alphanumeric strings with '=' padding, while plaintext credentials appear as readable text).Affected if Credentials are readable as plaintext strings in the configuration file.
If the Aqua Security Scanner plugin is installed and its configuration file contains readable (unencrypted) username, password, or API key values, the environment is affected by this vulnerability.
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 dataUpgrade to a patched version of the plugin that encrypts credentials at rest, or restrict filesystem access to the Jenkins master. Existing compromised credentials should be rotated.
Fix this in Aqua Security Scanner
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003069 — 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-1003069 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