dbcve.org
Digital.ai App Management PublisherApplication · Jenkins

CVE-2023-35148

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to after 2.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins Digital.ai App Management Publisher Plugin 2.6 and earlier allows attackers to connect to an attacker-specified URL, capturing credentials stored in Jenkins.

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 confidence

This is a CSRF vulnerability in the Digital.ai App Management Publisher Plugin for Jenkins. An attacker can trick an authenticated Jenkins user into making an unintended request that causes the plugin to connect to an attacker-controlled URL, potentially exfiltrating stored Jenkins credentials through that connection.

MitigationUpgrade the Digital.ai App Management Publisher Plugin to version 2.7 or later, which includes proper CSRF protection (crumb validation). Until then, minimize exposure by restricting Jenkins user permissions and monitoring for suspicious outbound connections.

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
Digital.ai App Management PublisherApplication
Affected:<= 2.6

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or check the plugin directory (typically $JENKINS_HOME/plugins/) for the 'digitalai-app-management-publisher' plugin folder.
    Affected if The Digital.ai App Management Publisher plugin is present on the Jenkins instance.
  2. Determine installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed, find 'Digital.ai App Management Publisher', and note the version number. Alternatively, check the version file inside the plugin folder (manifest or plugin's pom.xml).
    Affected if The installed version is 2.6 or lower.
  3. Check for active publisher configurations
    Navigate to a Jenkins job configuration page. Look for a 'Publish with Digital.ai App Management Publisher' post-build step or similar publisher configuration. Check job config XML files in $JENKINS_HOME/jobs/<jobname>/config.xml for '<digitalai-app-management-publisher>' entries.
    Affected if A job is configured to use the Digital.ai App Management Publisher publisher.
  4. Inspect plugin credential configurations
    Review Jenkins credentials (Manage Jenkins > Manage Credentials) for any credentials configured for or used by the Digital.ai App Management Publisher plugin. Also check job configurations for credentials bound to the plugin.
    Affected if The plugin has access to Jenkins credentials that could be exfiltrated.

The environment is affected if the Digital.ai App Management Publisher plugin version 2.6 or lower is installed AND configured in any job, as the CSRF flaw allows credential exfiltration through attacker-controlled URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.6
Interim mitigation

Upgrade the Digital.ai App Management Publisher Plugin to version 2.7 or later, which includes proper CSRF protection (crumb validation). Until then, minimize exposure by restricting Jenkins user permissions and monitoring for suspicious outbound connections.

Fix this in Digital.ai App Management Publisher Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35148 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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