Mail CommanderApplication · Jenkins
CVE-2020-2318
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 Mail Commander Plugin for Jenkins-ci Plugin 1.0.0 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller 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 confidenceThe Jenkins Mail Commander Plugin versions 1.0.0 and earlier stores SMTP passwords in plaintext within job config.xml files. These unencrypted credentials are accessible to any user with Extended Read permission on Jenkins jobs or anyone with filesystem-level access to the Jenkins controller.
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
Mail CommanderApplication
<= 1.0.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 Mail Commander Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Mail Commander', or inspect the plugin directory at $JENKINS_HOME/plugins/mail-commander/ for the presence of the plugin filesAffected if The Mail Commander plugin is found in the Jenkins plugins directory or plugin manager
-
Check the installed plugin versionLocate the plugin manifest file (META-INF/MANIFEST.MF) within the mail-commander plugin directory and read the Implementation-Version attribute, or view the version column in Manage Jenkins > Manage Plugins > InstalledAffected if The plugin version is 1.0.0 or any version earlier than 1.0.0
-
Identify jobs using Mail Commander configurationSearch job config.xml files in $JENKINS_HOME/jobs/*/config.xml for the presence of the <mail-commander> or <SMTP> configuration elements using grep or a similar search toolAffected if Any job config.xml files contain Mail Commander or SMTP-related configuration blocks
-
Verify if passwords are stored in plaintextExamine the identified config.xml files and check whether SMTP password fields contain plaintext strings (visible alphanumeric characters) rather than encrypted values or placeholder markersAffected if SMTP passwords in the config.xml files appear as readable plaintext strings rather than encrypted or masked values
-
Check access control on job configsReview Jenkins authorization matrix or matrix authorization strategy configuration at Manage Jenkins > Configure Global Security to determine which users have Extended Read permission on jobsAffected if Any user or group is granted Extended Read permission, allowing them to read job configuration files
You are affected if the Mail Commander Plugin version 1.0.0 or earlier is installed AND job config.xml files contain SMTP passwords stored as plaintext readable strings.
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 to a patched version of the Mail Commander Plugin if available, or remove the plugin if unused. Audit for and rotate any exposed SMTP passwords, and restrict Extended Read permission to only necessary users.
Fix this in Mail Commander
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2318 — 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-2020-2318 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