DelphixApplication · Jenkins
CVE-2023-40345
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 · uneditedJenkins Delphix Plugin 3.0.2 and earlier does not set the appropriate context for credentials lookup, allowing attackers with Overall/Read permission to access and capture credentials they are not entitled to.
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 versions 3.0.2 and earlier fails to set the proper security context when performing credentials lookups. This allows any user with basic Overall/Read permission to access and capture credentials stored in Jenkins that they are not entitled to, effectively bypassing Jenkins' credential access controls.
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.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.collect { it.shortName }.contains('delphix')Affected if The Delphix plugin appears in the installed plugins list
-
Check Delphix Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and find the Delphix Plugin version, or use the script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'delphix' }.versionAffected if The installed version is 3.0.2 or earlier
-
Check for stored credentials in JenkinsReview configured credentials via Manage Jenkins > Manage Credentials, or query the credentials store: CredentialsProvider.lookupCredentials(com.cloudbees.plugins.credentials.Credentials.class)Affected if Any credentials are stored in Jenkins (particularly those used by the Delphix Plugin)
-
Audit users with Overall/Read permissionIn Jenkins, go to Manage Jenkins > Manage Users and check which users have access, or use the script console: Jenkins.instance.authorizationStrategy.usersAffected if Any users exist with basic Overall/Read permission (which is the minimum required to exploit this flaw)
A user is affected if the Delphix Plugin version is 3.0.2 or earlier AND credentials are stored in Jenkins AND there are users with Overall/Read permission.
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.
From vendor dataUpdate the Delphix Plugin to a version newer than 3.0.2 once available, and audit exposed credentials to determine if any were compromised.
Fix this in Delphix
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40345 — 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-2023-40345 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