# CVE-2019-10446: Jenkins Cadence vManager Plugin disables SSL/TLS and hostname verification

> The plugin disables SSL/TLS verification globally, allowing attackers to intercept or modify traffic via man-in-the-middle attacks.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5j9f-5wmp-7f8h

## What is CVE-2019-10446?

CVE-2019-10446 is a high-severity vulnerability in Jenkins Cadence vManager Plugin, published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Cadence vManager Plugin 2.7.0 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2019-10446?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:vmanager-plugin` | Maven | All versions | 2.7.1 |
| `org.jenkins-ci.plugins:vmanager-plugin` | Maven | All versions | 2.7.1 |

Products: Jenkins Cadence Vmanager.

## How do I fix CVE-2019-10446?

Upgrade org.jenkins-ci.plugins:vmanager-plugin to 2.7.1 or later.

## Is CVE-2019-10446 being exploited?

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

## Other vulnerabilities in Jenkins Cadence vManager Plugin

- [CVE-2020-2243](https://insights.sbomify.com/CVE-2020-2243/): Stored XSS vulnerability in Jenkins Cadence vManager Plugin (medium 5.4)
- [CVE-2025-47886](https://insights.sbomify.com/CVE-2025-47886/): Jenkins Cadence vManager Plugin Vulnerable to Cross-Site Request Forgery (medium 4.3)
- [CVE-2025-47887](https://insights.sbomify.com/CVE-2025-47887/): Jenkins Cadence vManager Plugin is Missing Permission Checks (medium 4.3)
- [CVE-2025-31724](https://insights.sbomify.com/CVE-2025-31724/): Jenkins Cadence vManager Plugin Stores Verisium Manager vAPI keys Unencrypted (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10446 and fix it if it is affected.

What it is: CVE-2019-10446 is a high-severity vulnerability in Jenkins Cadence vManager Plugin, published on 16 Oct 2019. 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-2019-10446 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:vmanager-plugin (Maven): affected all versions; fixed in 2.7.1
- org.jenkins-ci.plugins:vmanager-plugin (Maven): affected all versions; fixed in 2.7.1

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-2019-10446/ (Markdown: https://insights.sbomify.com/CVE-2019-10446/index.md)
```

## Sources

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

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