Redgate Sql Change AutomationApplication · Jenkins
CVE-2019-16557
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 Redgate SQL Change Automation Plugin 2.0.3 and earlier stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or 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 Redgate SQL Change Automation Plugin versions 2.0.3 and earlier stores user credentials in plaintext within job config.xml files on the Jenkins master. These configuration files are readable by any user with Extended Read permission on Jenkins jobs, or by anyone with filesystem access to the Jenkins master server.
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
Redgate Sql Change AutomationApplication
<= 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.
-
Check if Redgate SQL Change Automation plugin is installedGo to Jenkins > Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar list-pluginsAffected if The plugin appears in the installed plugins list
-
Verify the plugin versionIn Manage Plugins > Installed, find 'Redgate SQL Change Automation' and check the version column; compare to 2.0.3Affected if The version is 2.0.3 or earlier
-
Identify jobs using the plugin with stored credentialsSearch job config.xml files for 'redgate' or 'sql-change-automation' strings, or review job configurations in the UI for Redgate build steps that store credentialsAffected if Any Jenkins job uses Redgate plugin steps with credential fields configured
-
Inspect job config.xml files for plaintext credentialsNavigate to $JENKINS_HOME/jobs/<jobname>/config.xml for each job using the plugin, or use Jenkins API: curl -u <user> http://<jenkins>/job/<jobname>/config.xmlAffected if The config.xml contains plaintext username/password values associated with Redgate configuration
-
Check Extended Read permission settingsGo to Jenkins > Manage Jenkins > Configure Global Security, or review matrix-based authorization settings for any user/group granted Overall/Extended Read accessAffected if Extended Read permission is granted to any user beyond administrators
You are affected if the Redgate SQL Change Automation plugin version is 2.0.3 or earlier AND any jobs using that plugin store credentials in job configurations, especially if Extended Read permission is enabled for non-admin users.
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 the plugin to a version that encrypts credentials (2.0.4 or later). As a compensating control, restrict Extended Read permission and limit filesystem access to the Jenkins master.
Fix this in Redgate Sql Change Automation
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16557 — 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-16557 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