DelphixApplication · Jenkins
CVE-2024-28161
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Jenkins Delphix Plugin 3.0.1, a global option for administrators to enable or disable SSL/TLS certificate validation for Data Control Tower (DCT) connections is disabled by default.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Delphix Plugin 3.0.1 has SSL/TLS certificate validation for Data Control Tower (DCT) connections disabled by default, potentially allowing man-in-the-middle attacks against DCT communications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DelphixApplication
= 3.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Delphix Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Delphix', or check the plugin manifest file in JENKINS_HOME/plugins/delphix/META-INF/MANIFEST.MFAffected if The plugin version is exactly 3.0.1
-
Check if DCT connection is configuredNavigate to Manage Jenkins > Configure System and look for Delphix plugin settings. Check if a Data Control Tower (DCT) connection URL/endpoint is configured in the plugin global configuration.Affected if A DCT connection URL is configured and the plugin is in use
-
Verify SSL/TLS certificate validation settingIn the Delphix plugin global configuration section, locate the SSL/TLS certificate validation option for DCT connections and verify whether it is enabled or disabled.Affected if SSL/TLS certificate validation is disabled (unchecked) for DCT connections
You are affected if Jenkins has Delphix Plugin version 3.0.1 installed with a DCT connection configured and SSL/TLS certificate validation disabled for that connection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedEnable SSL/TLS certificate validation in the plugin's global configuration settings and ensure the default is changed to enabled in future releases.
- Log in to Jenkins as an administrator
- Navigate to Manage Jenkins > Global Tool Configuration or the Delphix Plugin configuration page
- Locate the SSL/TLS certificate validation setting for Data Control Tower (DCT) connections
- Enable SSL/TLS certificate validation (change from disabled to enabled)
- Save the configuration
- Verify the DCT connection works correctly with certificate validation enabled
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Delphix
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28161 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28161 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data