Jenkins SAML Single Sign On(SSO) Plugin missing hostname validation

Exploitation

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

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2023-32993: 0.21% estimated exploitation activity in the next 30 days; percentile 11.12 (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.

Jenkins SAML Single Sign On(SSO) Plugin 2.0.2 and earlier does not perform hostname validation when connecting to miniOrange or the configured IdP to retrieve SAML metadata. This lack of validation could be abused using a man-in-the-middle attack to intercept these connections. SAML Single Sign On(SSO) Plugin 2.1.0 performs hostname validation when connecting to miniOrange or the configured IdP to retrieve SAML metadata.

Published by the source

16 May 2023, 18:30 UTC

Last modified by the source

23 Jan 2025, 23:16 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6v6h-rw43-97fh

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

# Patch Next advisory brief: CVE-2023-32993

Advisory: Jenkins SAML Single Sign On(SSO) Plugin missing hostname validation
IDs: CVE-2023-32993, GHSA-6v6h-rw43-97fh
Record: https://patchnext.com/advisories/cve-2023-32993 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.jenkins.plugins:miniorange-saml-sp 2.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jenkins.plugins:miniorange-saml-sp: affected < 2.1.0; fixed in 2.1.0

## Suggested inspection (read-only)
- Maven io.jenkins.plugins:miniorange-saml-sp: 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 io.jenkins.plugins:miniorange-saml-sp.
- 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-6v6h-rw43-97fh (GitHub-reviewed advisory GHSA-6v6h-rw43-97fh lists affected ranges: Maven io.jenkins.plugins:miniorange-saml-sp >=0 <2.1.0)

Commands are suggestions: review each one before running it.