dbcve.org
Active DirectoryApplication · Jenkins

CVE-2019-1003009

HIGH · 7.4 CVSS v3.0 Published 2019-02-06
Fix available
A fix is available. Upgrade to after 2.10 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An improper certificate validation vulnerability exists in Jenkins Active Directory Plugin 2.10 and earlier in src/main/java/hudson/plugins/active_directory/ActiveDirectoryDomain.java, src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java, src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java that allows attackers to impersonate the Active Directory server Jenkins connects to for authentication if Jenkins is configured to use StartTLS.

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 confidence

The Jenkins Active Directory plugin versions 2.10 and earlier fails to properly validate SSL/TLS certificates when StartTLS is enabled for Active Directory authentication. This allows a man-in-the-middle attacker to impersonate the AD server by presenting a fraudulent certificate, potentially gaining access to credentials and authenticated sessions.

MitigationUpdate Jenkins Active Directory plugin to version 2.11 or later, which contains proper certificate chain validation. Alternatively, ensure the AD server's certificate is properly trusted in the Java truststore and verify StartTLS connections are using proper hostname verification.

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
Active DirectoryApplication
Affected:<= 2.10

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Active Directory plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and look for 'Active Directory' plugin in the list, or check the $JENKINS_HOME/plugins directory for the active-directory plugin folder
    Affected if The Active Directory plugin is present in the Jenkins instance
  2. Check the installed plugin version
    In Manage Jenkins > Manage Plugins > Installed, find the Active Directory plugin and note the Version column; alternatively, examine the $JENKINS_HOME/plugins/active-directory/META-INF/MANIFEST.MF file for the Plugin-Version attribute
    Affected if The version is 2.10 or earlier
  3. Determine if StartTLS is enabled for AD authentication
    Navigate to Manage Jenkins > Configure Global Security > Active Directory domain configuration; inspect the domain settings for the StartTLS option being checked/enabled, or review the $JENKINS_HOME/credentials.xml and related configuration files for StartTLS settings
    Affected if StartTLS is enabled in the Active Directory domain configuration
  4. Verify the AD server certificate trust configuration
    Examine the Java cacerts truststore (typically $JAVA_HOME/lib/security/cacerts or a custom truststore configured in Jenkins > Manage Jenkins > Configure Java) to confirm the AD server's certificate is properly imported and trusted
    Affected if The AD server certificate is not properly trusted in the Java truststore or a custom truststore configured for Jenkins
  5. Confirm hostname verification status for StartTLS connections
    Review Jenkins startup parameters and any custom Java options (-D flags) for SSL/TLS hostname verification settings, and check if the AD plugin configuration explicitly disables hostname verification
    Affected if Hostname verification is disabled or not properly enforced for StartTLS connections to the AD server

The environment is affected if the Jenkins Active Directory plugin version is 2.10 or earlier AND StartTLS is enabled for authentication, regardless of truststore configuration status.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.10
Interim mitigation

Update Jenkins Active Directory plugin to version 2.11 or later, which contains proper certificate chain validation. Alternatively, ensure the AD server's certificate is properly trusted in the Java truststore and verify StartTLS connections are using proper hostname verification.

Fix this in Active Directory Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003009 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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