dbcve.org
Digital.ai App Management PublisherApplication · Jenkins

CVE-2023-35149

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 →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 missing permission check in Jenkins Digital.ai App Management Publisher Plugin 2.6 and earlier allows attackers with Overall/Read permission 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

The Digital.ai App Management Publisher Plugin for Jenkins lacks proper permission checks in certain endpoints, allowing any user with Overall/Read permission (the lowest privilege) to trigger Jenkins to make HTTP connections to attacker-controlled URLs. This SSRF-like behavior can be leveraged to exfiltrate stored Jenkins credentials.

MitigationUpdate Digital.ai App Management Publisher Plugin to version 2.7 or later which contains the permission check fix. If immediate update is not possible, restrict Overall/Read permission to only trusted users and consider network segmentation.

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
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 checks

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

  1. Verify Digital.ai App Management Publisher Plugin is installed
    Access Jenkins plugin management UI or use CLI to list installed plugins and locate 'digitalai-app-management-publisher' or similar
    Affected if Plugin is present in the Jenkins instance
  2. Check installed plugin version
    View the plugin details in Jenkins plugin manager to see the version number
    Affected if Version is 2.6 or lower (any version <= 2.6 is affected)
  3. Confirm Overall/Read permission configuration
    Review Jenkins user permissions matrix or global security settings to identify which users or groups have Overall/Read permission
    Affected if Any untrusted or anonymous users have Overall/Read permission enabled
  4. Check for exposed plugin endpoints
    Inspect network logs or plugin configuration for outbound HTTP requests initiated by the plugin, particularly requests to external URLs
    Affected if Jenkins is making outbound HTTP connections to URLs that were not configured by administrators

A user is affected if the Digital.ai App Management Publisher Plugin version 2.6 or lower is installed AND at least one untrusted user has Overall/Read permission, allowing them to trigger arbitrary HTTP connections.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.6
Interim mitigation

Update Digital.ai App Management Publisher Plugin to version 2.7 or later which contains the permission check fix. If immediate update is not possible, restrict Overall/Read permission to only trusted users and consider network segmentation.

Recommended fix High confidence

Upgrade to Digital.ai App Management Publisher plugin version 2.7 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Search for 'Digital.ai App Management Publisher'
  4. 4. If an update is available, select the plugin and click 'Update'
  5. 5. Restart Jenkins to apply the update
  6. 6. Verify the new version is installed under Manage Jenkins > Manage Plugins > Installed
Caveat Review plugin release notes for any configuration changes required after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital.ai App Management Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35149 — 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-35149 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