dbcve.org
Subversion Partial Release ManagerApplication · Jenkins

CVE-2024-34148

MEDIUM · 6.8 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
74/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
Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier programmatically disables the fix for CVE-2016-3721 whenever a build is triggered from a release tag, by setting the Java system property 'hudson.model.ParametersAction.keepUndefinedParameters'.

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 Subversion Partial Release Manager Plugin version 1.0.1 and earlier contains code that programmatically disables the security fix for CVE-2016-3721 by setting the Java system property 'hudson.model.ParametersAction.keepUndefinedParameters' to true whenever a build is triggered from a release tag. This re-enables the vulnerable behavior that allowed arbitrary parameters to be passed to builds, potentially enabling an attacker to exploit the original arbitrary file read vulnerability.

MitigationUpgrade to a patched version of the Subversion Partial Release Manager Plugin once available, or remove/disable the plugin if not essential. Alternatively, monitor and restrict who can trigger builds from release tags.

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
Subversion Partial Release ManagerApplication
Affected:<= 1.0.1

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 Subversion Partial Release Manager Plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Subversion Partial Release Manager' or check the plugin directory $JENKINS_HOME/plugins for subversion-release-manager or similar plugin folder
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Subversion Partial Release Manager plugin and note the version column. If using CLI, check the plugin's manifest.xml or .hpi file for the Version element
    Affected if The version is 1.0.1 or any version earlier than 1.0.1
  3. Identify if release tag builds are triggered
    Review Jenkins job configurations for any jobs using the Subversion Partial Release Manager plugin functionality to trigger builds from release tags. Check job configuration pages for release tag related parameters or triggers
    Affected if Jobs are configured to trigger builds from release tags using this plugin
  4. Check for the vulnerable system property setting
    Inspect build logs or system information for 'hudson.model.ParametersAction.keepUndefinedParameters=true' being set. This can also be checked via Jenkins > Manage Jenkins > System Information > System Properties
    Affected if The property hudson.model.ParametersAction.keepUndefinedParameters is set to true, especially during release tag builds

If the Subversion Partial Release Manager Plugin version 1.0.1 or earlier is installed AND builds from release tags are triggered using this plugin, the environment is affected by this vulnerability.

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

Upgrade to a patched version of the Subversion Partial Release Manager Plugin once available, or remove/disable the plugin if not essential. Alternatively, monitor and restrict who can trigger builds from release tags.

Fix this in Subversion Partial Release Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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