dbcve.org
Assembla Merge Request BuilderApplication · Jenkins

CVE-2023-30521

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-12
Fix available
A fix is available. Upgrade to after 1.1.13 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Assembla merge request builder Plugin 1.1.13 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository.

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 merge request builder Plugin versions 1.1.13 and earlier lacks authorization checks on an endpoint that triggers builds. Unauthenticated attackers can send requests to invoke build operations for jobs associated with attacker-specified repositories by manipulating input parameters.

MitigationUpgrade the Assembla merge request builder Plugin to version 1.1.14 or later, which includes proper permission validation before executing build triggers.

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 Merge Request BuilderApplication
Affected:<= 1.1.13

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check if Assembla Merge Request Builder plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Assembla Merge Request Builder', or run: jenkins-plugin-cli --list | grep assembla
    Affected if The plugin appears in the installed plugins list
  2. Verify the installed plugin version
    In the Installed plugins page, locate the Assembla Merge Request Builder plugin and note the Version column. Alternatively, examine the plugin manifest file in $JENKINS_HOME/plugins/assembla-merge-request-builder/META-INF/MANIFEST.MF
    Affected if Version is 1.1.13 or earlier
  3. Check for jobs using the Assembla plugin
    Search for jobs configured with Assembla merge request builder: Go to Manage Jenkins > Script Console and run: Jenkins.instance.items.findAll { it.builders.any { it.getClass().getName().contains('Assembla') } }.collect { it.fullName }
    Affected if Any jobs are returned that use the Assembla merge request builder configuration
  4. Verify the build trigger endpoint is accessible
    The vulnerable endpoint typically accepts parameters like 'repository' and 'token' to trigger builds. Check if the Jenkins instance allows unauthenticated access to build triggers related to Assembla by reviewing security configuration at Manage Jenkins > Configure Global Security
    Affected if Anonymous users have Overall/Read or build trigger permissions enabled

A user is affected if the Assembla Merge Request Builder plugin is installed at version 1.1.13 or earlier and has jobs configured that use this plugin's build triggers.

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.1.13
Interim mitigation

Upgrade the Assembla merge request builder Plugin to version 1.1.14 or later, which includes proper permission validation before executing build triggers.

Recommended fix Moderate confidence

1.1.14 or later (check Jenkins Plugin Index for latest available version)

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the 'Assembla merge request builder' plugin
  5. If the installed version is 1.1.13 or earlier, click 'Update now' to upgrade to the latest version
  6. Alternatively, download the latest version from the Jenkins plugin repository and manually upload it
  7. After upgrade, go to Manage Jenkins > Manage Old Data to clean up any deprecated data
  8. Restart Jenkins if required

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

Fix this in Assembla Merge Request Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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