Jenkins Active Directory Plugin Improper certificate validation with StartTLS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2019-1003009: 0.78% estimated exploitation activity in the next 30 days; percentile 55.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An improper certificate validation vulnerability exists in Jenkins Active Directory Plugin 2.10 and earlier in src/main/java/hudson/plugins/activedirectory/ActiveDirectoryDomain.java, src/main/java/hudson/plugins/activedirectory/ActiveDirectorySecurityRealm.java, src/main/java/hudson/plugins/activedirectory/ActiveDirectoryUnixAuthenticationProvider.java that allows attackers to impersonate the Active Directory server Jenkins connects to for authentication if Jenkins is configured to use StartTLS.

Published by the source

13 May 2022, 01:31 UTC

Last modified by the source

9 Jan 2024, 17:59 UTC

Source last checked

26 Oct 2026, 16:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2h95-4xw9-m68j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-1003009

Advisory: Jenkins Active Directory Plugin Improper certificate validation with StartTLS
IDs: CVE-2019-1003009, GHSA-2h95-4xw9-m68j
Record: https://patchnext.com/advisories/cve-2019-1003009 (revision 1, source checked 26 Oct 2026, 16:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:active-directory 2.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:active-directory: affected <= 2.10; fixed in 2.11

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:active-directory: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:active-directory.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2h95-4xw9-m68j (GitHub-reviewed advisory GHSA-2h95-4xw9-m68j lists affected ranges: Maven org.jenkins-ci.plugins:active-directory >=0 <=2.10)

Commands are suggestions: review each one before running it.