dbcve.org
Amazon Sns Build NotifierApplication · Jenkins

CVE-2019-1003063

HIGH · 8.8 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Jenkins Amazon SNS Build Notifier 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 confidence

The Jenkins Amazon SNS Build Notifier Plugin stores AWS credentials in plaintext within its global configuration XML file on the Jenkins master filesystem. Any user with access to the Jenkins controller's file system can read these configuration files and obtain the AWS access keys in cleartext.

MitigationMigrate credentials to Jenkins' built-in credential store using the Credentials Plugin API, which encrypts credentials at rest and controls access through Jenkins' permission model. Alternatively, restrict filesystem access to the Jenkins home directory to only authorized administrators.

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
Amazon Sns Build NotifierApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if the Amazon SNS Build Notifier plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins. Look for 'Amazon SNS Build Notifier' in the list.
    Affected if The plugin appears in the installed plugins list, meaning it is present in the environment.
  2. Locate the plugin's global configuration XML file
    The global configuration for Jenkins plugins is typically stored in $JENKINS_HOME/org.jenkins-ci.plugins.amazon-sns-build-notifier.xml or $JENKINS_HOME/plugins/amazon-sns-build-notifier/config.xml. Check the $JENKINS_HOME directory for an XML file associated with this plugin.
    Affected if A configuration XML file for the Amazon SNS Build Notifier plugin exists in the Jenkins home directory.
  3. Inspect the configuration file for plaintext AWS credentials
    Open the identified XML configuration file in a text editor or use grep to search for AWS-related fields: grep -i 'accesskey\|secretkey\|aws' $JENKINS_HOME/org.jenkins-ci.plugins.amazon-sns-build-notifier.xml. Look for plaintext string values containing AWS access key IDs or secret access keys.
    Affected if The configuration file contains plaintext AWS access key IDs (typically 20 characters starting with AKIA) or secret access keys in cleartext between XML tags.
  4. Check filesystem permissions on the configuration file
    Run ls -la on the configuration file to review read permissions: ls -la $JENKINS_HOME/org.jenkins-ci.plugins.amazon-sns-build-notifier.xml. Also check the parent directory permissions.
    Affected if The configuration file is readable by users other than the Jenkins service account, or the Jenkins home directory has overly permissive access controls.

A user is affected if the Amazon SNS Build Notifier plugin is installed and its configuration XML file contains plaintext AWS credentials that are accessible to any user with filesystem access to the Jenkins home directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Migrate credentials to Jenkins' built-in credential store using the Credentials Plugin API, which encrypts credentials at rest and controls access through Jenkins' permission model. Alternatively, restrict filesystem access to the Jenkins home directory to only authorized administrators.

Fix this in Amazon Sns Build Notifier Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003063 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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