dbcve.org
Assembla AuthApplication · Jenkins

CVE-2023-41945

HIGH · 8.8 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to after 1.14 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Jenkins Assembla Auth Plugin 1.14 and earlier does not verify that the permissions it grants are enabled, resulting in users with EDIT permissions to be granted Overall/Manage and Overall/SystemRead permissions, even if those permissions are disabled and should not be granted.

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 Jenkins Assembla Auth Plugin versions 1.14 and earlier fails to validate whether permissions are enabled before granting them. Users with EDIT permissions incorrectly receive Overall/Manage and Overall/SystemRead permissions even when those permissions have been explicitly disabled in the configuration, representing a privilege escalation or permission bypass vulnerability.

MitigationUpgrade the Assembla Auth Plugin to version 1.15 or later which implements proper permission verification before granting access. Alternatively, review user permissions and disable any unauthorized grants until the upgrade can be applied.

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
Assembla AuthApplication
Affected:<= 1.14

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
High
Availability
High

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

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 Assembla Auth Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the JENKINS_HOME/plugins directory for the assembla-auth plugin folder. Identify the plugin version from the manifest or plugin details.
    Affected if Assembla Auth Plugin version 1.14 or earlier is installed and the plugin is present in the Jenkins environment
  2. Confirm Assembla authentication is enabled
    Navigate to Manage Jenkins > Configure Global Security > Access Control (or Security Realm). Verify that 'Assembla' is selected as the Security Realm, indicating Assembla authentication is active.
    Affected if Assembla is configured as the authentication method; the vulnerability only applies when Assembla authentication is in use
  3. Review user permissions against configuration
    Navigate to Manage Jenkins > Manage and Assign Roles > Assign Roles (or similar role management if configured). Identify users with EDIT permissions. Then check the Assembla plugin configuration to see which permissions are explicitly enabled or disabled. Compare granted permissions against intended settings.
    Affected if Users with EDIT permissions have been granted Overall/Manage or Overall/SystemRead permissions even though those permissions are explicitly disabled in the plugin configuration; this indicates the vulnerability is present
  4. Audit overall permissions for Assembla users
    Use the Jenkins script console or user management view to list all users authenticated via Assembla and their assigned Overall permissions. Look for unexpected Overall/Manage or Overall/SystemRead grants.
    Affected if Any Assembla-authenticated user possesses Overall/Manage or Overall/SystemRead permissions that were not intentionally assigned through proper configuration

You are affected if the Assembla Auth Plugin version 1.14 or earlier is installed, Assembla authentication is configured as the security realm, and users have obtained permissions they should not have based on the plugin's configuration settings.

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 1.14
Interim mitigation

Upgrade the Assembla Auth Plugin to version 1.15 or later which implements proper permission verification before granting access. Alternatively, review user permissions and disable any unauthorized grants until the upgrade can be applied.

Recommended fix Moderate confidence

Version 1.15 or later

  1. Check the Jenkins plugin repository (https://plugins.jenkins.io/assembla-auth/) or Jenkins Security Advisory for the fixed version of the Assembla Auth plugin
  2. Upgrade the Assembla Auth plugin to the fixed version (version 1.15 or higher) via Jenkins Plugin Manager or by updating plugin dependencies
  3. After upgrade, verify that the permission handling now correctly checks if permissions are enabled before granting them
  4. Review user permissions in Jenkins to ensure only intended permissions are granted

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

Fix this in Assembla Auth Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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