Azure Publishersettings CredentialsApplication · Jenkins
CVE-2019-10303
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 Azure PublisherSettings Credentials Plugin 1.2 and earlier stored credentials unencrypted in the credentials.xml file on the Jenkins master where they could 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 Azure PublisherSettings Credentials Plugin for Jenkins versions 1.2 and earlier stores Azure credentials in plaintext within the credentials.xml file on the Jenkins master filesystem. Any user with file system access to the Jenkins master can read these unencrypted credentials directly from the configuration file.
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
Azure Publishersettings CredentialsApplication
<= 1.2CVSS 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.
-
Identify if the Azure PublisherSettings Credentials Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Azure Publishersettings Credentials' or 'Azure PublisherSettings Credentials', or inspect the plugin directory within the Jenkins plugins folder for azure-credentials or similar naming.Affected if The plugin is present in the installed plugins list or filesystem.
-
Determine the installed plugin versionIn the Manage Plugins > Installed tab, locate the plugin and note the version number displayed, or examine the plugin's manifest (.hpi or .jpi file) for the version metadata.Affected if The version is 1.2 or earlier.
-
Locate the credentials.xml configuration fileFind the credentials.xml file in the Jenkins home directory (commonly $JENKINS_HOME/credentials.xml) which stores all Jenkins credentials configurations.Affected if The credentials.xml file exists on the Jenkins master filesystem.
-
Inspect credentials.xml for Azure PublisherSettings entriesOpen credentials.xml and search for entries containing 'azure-publishersettings' or 'AzurePublisherSettings' in the ID or type fields, or look for credential definitions matching Azure publish settings.Affected if Credentials with Azure PublisherSettings type exist in the file.
-
Verify plaintext storage of Azure credentialsExamine the specific Azure credential entries in credentials.xml and check whether the secret/credential value appears as plaintext XML content rather than an encrypted reference (look for unencrypted GUIDs, subscription IDs, or publish settings XML content).Affected if The credential values are stored as plaintext strings within the XML rather than being encrypted or referenced externally.
The environment is affected if the Azure PublisherSettings Credentials Plugin version 1.2 or earlier is installed AND Azure credentials are stored in the plaintext credentials.xml file.
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 Azure PublisherSettings Credentials Plugin to version 1.3 or later which implements encryption for stored credentials. As immediate mitigation, restrict filesystem access to the Jenkins master and rotate any credentials that may have been exposed.
Fix this in Azure Publishersettings Credentials
Scoped from the published advisory
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10303 — 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-10303 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