dbcve.org
Aws Elastic Beanstalk PublisherApplication · Jenkins

CVE-2019-1003052

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 AWS Elastic Beanstalk Publisher 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 AWS Elastic Beanstalk Publisher Plugin stores AWS credentials in plaintext within its global configuration file on the Jenkins master. Users with file system access to the Jenkins master can read these unencrypted credentials directly from the configuration file, leading to credential exposure.

MitigationMigrate credentials to Jenkins' built-in Credentials API which provides encrypted storage. If immediate remediation is required, restrict file system access to the Jenkins configuration directory and rotate any exposed 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
Aws Elastic Beanstalk PublisherApplication
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 the AWS Elastic Beanstalk Publisher plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'AWS Elastic Beanstalk' or 'aws-elastic-beanstalk-publisher' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Locate the plugin global configuration file
    The plugin stores its configuration in the Jenkins home directory under hudson.plugins.aws_elastic_beanstalk.AwsElasticBeanstalkPublisher.xml or similar path within the Jenkins config directory. Check the Jenkins $JENKINS_HOME directory for this file.
    Affected if The configuration file exists for this plugin.
  3. Determine if the plugin has been configured with AWS credentials
    Open the configuration file identified in the previous step and examine its contents for AWS access key, secret key, or credential-related XML elements.
    Affected if The configuration file contains AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, or similar credential fields with actual values.
  4. Verify credentials are stored in plaintext
    Examine the credential values in the configuration file. If they appear as plain text strings rather than IDs referencing Jenkins Credentials API (such as <credentialsId> tags pointing to credentials stored in the built-in credentials store), they are stored in plaintext.
    Affected if Credential values appear as plaintext strings rather than as references to the Jenkins Credentials API.
  5. Check if credentials use Jenkins Credentials API instead
    Review the configuration file for elements like <credentialsId> that reference credentials stored via Jenkins > Manage Jenkins > Manage Credentials. If such references exist and no plaintext keys are present, the plugin is using the safer built-in storage.
    Affected if No plaintext AWS keys are found and credentials are properly referenced through the Jenkins Credentials API.

The environment is affected if the AWS Elastic Beanstalk Publisher plugin is installed, has been configured with AWS credentials, and those credentials are stored as plaintext values in the plugin configuration file rather than referenced through Jenkins Credentials API.

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 Credentials API which provides encrypted storage. If immediate remediation is required, restrict file system access to the Jenkins configuration directory and rotate any exposed credentials.

Fix this in Aws Elastic Beanstalk Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003052 — 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-1003052 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