# CVE-2017-2649: Jenkins Active Directory Plugin did not verify certificate of AD server

> The Jenkins Active Directory plugin fails to verify server certificates, allowing attackers to perform Man-in-the-Middle attacks and intercept authentication data.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vcgj-j8c5-2h52

## What is CVE-2017-2649?

CVE-2017-2649 is a high-severity vulnerability in Active Directory Jenkins plugin, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that the Active Directory Plugin for Jenkins up to and including version 2.2 did not verify certificates of the Active Directory server, thereby enabling Man-in-the-Middle attacks.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2017-2649?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:active-directory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:active-directory` | Maven | All versions | 2.3 |
| `org.jenkins-ci.plugins:active-directory` | Maven | All versions | 2.3 |

Products: Jenkins Active Directory.

## How do I fix CVE-2017-2649?

Upgrade org.jenkins-ci.plugins:active-directory to 2.3 or later.

## Is CVE-2017-2649 being exploited?

There is no known exploitation of CVE-2017-2649 in the wild and no public exploit code.

## Other vulnerabilities in Active Directory Jenkins plugin

- [CVE-2020-2299](https://insights.sbomify.com/CVE-2020-2299/): Improper Authentication in Jenkins Active Directory Plugin (critical 9.8)
- [CVE-2020-2300](https://insights.sbomify.com/CVE-2020-2300/): Improper Authentication (empty password) in Jenkins Active Directory Plugin (critical 9.8)
- [CVE-2020-2301](https://insights.sbomify.com/CVE-2020-2301/): Authentication cache in Active Directory Jenkins Plugin allows logging in with any password (critical 9.8)
- [CVE-2019-1003009](https://insights.sbomify.com/CVE-2019-1003009/): Jenkins Active Directory Plugin Improper certificate validation with StartTLS (high 7.4)
- [CVE-2026-48918](https://insights.sbomify.com/CVE-2026-48918/): Jenkins Active Directory Plugin follows LDAP referrals by default (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2649 and fix it if it is affected.

What it is: CVE-2017-2649 is a high-severity vulnerability in Active Directory Jenkins plugin, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2649 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:active-directory (Maven): affected all versions; fixed in 2.3
- org.jenkins-ci.plugins:active-directory (Maven): affected all versions; fixed in 2.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-2649/ (Markdown: https://insights.sbomify.com/CVE-2017-2649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-2649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-2649
- OSV: https://osv.dev/vulnerability/CVE-2017-2649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-2649/
Summaries are generated and may contain mistakes; the official description above is the record.