Aws CodedeployApplication · Jenkins
CVE-2018-1000403
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 project Jenkins AWS CodeDeploy Plugin version 1.19 and earlier contains a Insufficiently Protected Credentials vulnerability in AWSCodeDeployPublisher.java that can result in Credentials Disclosure. This attack appear to be exploitable via local file access. This vulnerability appears to have been fixed in 1.20 and later.
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 AWS CodeDeploy Plugin versions 1.19 and earlier stores credentials insecurely in AWSCodeDeployPublisher.java, allowing local attackers with file system access to retrieve exposed credentials. The vulnerability stems from insufficient protection mechanisms for stored 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 CodedeployApplication
<= 1.19CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 the installed Jenkins AWS CodeDeploy Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin's manifest file (the .jpi or .hpi file in JENKINS_HOME/plugins/). Compare the version number to the affected range: version 1.19 or earlier.Affected if The installed version is 1.19 or earlier.
-
Confirm the plugin is in useCheck Jenkins job configurations for any jobs using the 'AWS CodeDeploy Publisher' post-build action, or inspect the JENKINS_HOME/jobs/ directory for job XML configs containing 'AWSCodeDeployPublisher'.Affected if The plugin is actively configured in one or more Jenkins jobs.
-
Locate the vulnerable fileAccess the Jenkins controller file system and locate AWSCodeDeployPublisher.java or its compiled class in the plugin JAR. In a default installation this may be under JENKINS_HOME/plugins/aws-codedeploy/.Affected if The plugin file exists on the Jenkins controller file system, indicating the plugin is installed.
-
Assess local file system access exposureReview file permissions on JENKINS_HOME/ and subdirectories. Verify whether untrusted local users or processes have read access to the plugin directory or stored credential files.Affected if Local untrusted users or processes have read access to Jenkins home directory contents.
You are affected if the Jenkins AWS CodeDeploy Plugin version is 1.19 or earlier, the plugin is configured with credentials in use, and local attackers could access the Jenkins file system.
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 Jenkins AWS CodeDeploy Plugin to version 1.20 or later to receive the credential protection fix. If upgrading is not immediately possible, restrict local file system access and rotate any credentials that may have been exposed.
Fix this in Aws Codedeploy
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2018-1000403 — 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-2018-1000403 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