# CVE-2022-38666: SSL/TLS certificate validation unconditionally disabled by Jenkins NS-ND Integration Performance Publisher Plugin

> The Jenkins NS-ND Integration Performance Publisher Plugin disables SSL/TLS validation, allowing attackers to bypass security checks and potentially intercept traffic.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-vj5r-mmp4-3hrx

## What is CVE-2022-38666?

CVE-2022-38666 is a high-severity vulnerability in Jenkins NS-ND Integration Performance Publisher Plugin, published on 15 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins NS-ND Integration Performance Publisher Plugin 4.8.0.146 and earlier unconditionally disables SSL/TLS certificate and hostname validation for several features.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-38666?

2 open source packages ship an affected version, including org.jenkins-ci.main:cavisson-ns-nd-integration. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.main:cavisson-ns-nd-integration` | Maven | All versions to 4.8.0.146 | None |
| `org.jenkins-ci.main:cavisson-ns-nd-integration` | Maven | All versions to 4.8.0.146 | None |

Products: Jenkins Ns-Nd Integration Performance Publisher.

## How do I fix CVE-2022-38666?

No fix has been published for CVE-2022-38666 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-38666 being exploited?

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

## Other vulnerabilities in Jenkins NS-ND Integration Performance Publisher Plugin

- [CVE-2022-41227](https://insights.sbomify.com/CVE-2022-41227/): Jenkins NS-ND Integration Performance Publisher Plugin vulnerable to Cross-Site Request Forgery (high 8.8)
- [CVE-2022-41228](https://insights.sbomify.com/CVE-2022-41228/): Jenkins NS-ND Integration Performance Publisher Plugin vulnerable to Missing Authorization (high 8.8)
- [CVE-2023-33000](https://insights.sbomify.com/CVE-2023-33000/): Jenkins NS-ND Integration Performance Publisher Plugin displays credentials without masking (high 7.5)
- [CVE-2022-45391](https://insights.sbomify.com/CVE-2022-45391/): Jenkins NS-ND Integration Performance Publisher Plugin disables SSL/TLS certificate validation globally and unconditionally (high 7.5)
- [CVE-2022-45392](https://insights.sbomify.com/CVE-2022-45392/): Plaintext Storage of a Password in Jenkins NS-ND Integration Performance Publisher Plugin (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38666 and fix it if it is affected.

What it is: CVE-2022-38666 is a high-severity vulnerability in Jenkins NS-ND Integration Performance Publisher Plugin, published on 15 Nov 2022. 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-2022-38666 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.main:cavisson-ns-nd-integration (Maven): affected all versions up to 4.8.0.146; no fix listed
- org.jenkins-ci.main:cavisson-ns-nd-integration (Maven): affected all versions up to 4.8.0.146; no fix listed

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

## Sources

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

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