Ec2Application · Jenkins
CVE-2019-10364
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 Amazon EC2 Plugin 1.43 and earlier wrote the beginning of private keys to the Jenkins system log.
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 Amazon EC2 Plugin versions 1.43 and earlier had a logging flaw where the beginning portion of SSH private keys was being written to the Jenkins system log. This exposed sensitive credential material through logs that may be accessible to unauthorized users, representing an information disclosure vulnerability.
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
Ec2Application
<= 1.43CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Amazon EC2 Plugin is installedNavigate to Jenkins Manage Plugins > Installed and look for 'Amazon EC2' plugin in the list. Note the installed version number shown.Affected if Plugin version 1.43 or earlier is listed
-
Verify EC2 cloud configuration existsGo to Jenkins > Manage Jenkins > Configure Clouds (or EC2 configuration page). Check if any EC2 cloud entries are configured with SSH private key credentials.Affected if EC2 cloud is configured and using SSH key authentication
-
Search logs for private key materialLocate the Jenkins system log files (typically found in $JENKINS_HOME/logs or the journal/logs directory). Search for patterns matching the beginning of SSH private keys, such as '-----BEGIN RSA PRIVATE KEY-----' or similar PEM header strings.Affected if Log files contain any SSH private key material or PEM-formatted credential headers
-
Review historical logs if current version is patchedIf the plugin has been upgraded to version 1.44 or later, review archived or historical log files that existed before the upgrade for any exposed private key content.Affected if Historical logs contain private key material from before patching
The environment is affected if the Amazon EC2 Plugin version is 1.43 or earlier and EC2 clouds were configured with SSH private key credentials, as the private key material may have been written to system logs.
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 Amazon EC2 Plugin to version 1.44 or later to remediate the private key logging issue. Review historical Jenkins system logs for any potential exposure of private key material.
Fix this in Ec2
Scoped from the published advisory
- Consultation1.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10364 — 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-10364 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