Ldap EmailApplication · Jenkins
CVE-2019-10434
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 LDAP Email Plugin transmits configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure.
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 LDAP Email Plugin stores and transmits configured LDAP credentials in plain text as part of the global Jenkins configuration form. This exposes credentials during form submission, potentially logging them or transmitting them in cleartext over the network.
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
Ldap EmailApplication
<= 0.8CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if LDAP Email plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'LDAP Email' or 'ldap-email-plugin' in the list of installed pluginsAffected if The plugin is not installed in Jenkins
-
Verify the installed plugin versionIn the plugin manager's Installed tab, locate the LDAP Email plugin and note the version number displayedAffected if The installed version is 0.8 or lower (any version <= 0.8)
-
Inspect global configuration for plain text LDAP credentialsNavigate to Manage Jenkins > Configure Global Security or Configure System. Locate the LDAP Email section (or LDAP configuration area) and examine whether the bindPassword, adminPassword, or similar credential fields display plain text rather than masked characters or credential binding markersAffected if LDAP credentials (bind password, admin password, or similar) appear as visible plain text in the configuration form rather than being masked, encrypted, or referenced as credentials ID
A user is affected if the LDAP Email plugin version is 0.8 or lower AND plain text LDAP credentials are visible in the Jenkins global configuration form.
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 dataReplace plain text credential storage with Jenkins' built-in credential binding mechanisms (e.g., Secret text credentials or Credentials Binding plugin) to properly encrypt sensitive values at rest and in transit.
Fix this in Ldap Email
Scoped from the published advisory
- Consultation3.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10434 — 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-10434 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