CVE-2018-1000402 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in com.amazonaws:codedeploy. A fix is available for com.amazonaws:codedeploy — see the affected versions and patch details below.
Jenkins AWS CodeDeploy Plugin has Insufficiently Protected Credentials
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.amazonaws:codedeployReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins project Jenkins AWS CodeDeploy Plugin version 1.19 and earlier contains a File and Directory Information Exposure vulnerability in AWSCodeDeployPublisher.java that can result in Disclosure of environment variables. This vulnerability appears to have been fixed in 1.20 and later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.amazonaws:codedeploy | all versions | 1.20com.amazonaws:codedeploy:1.20 |
Affected Products
aws codedeployjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazonaws:codedeploy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.amazonaws:codedeploy to 1.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000402 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2018-1000402 in your dependencies?
Find it across Maven, including transitive dependencies.