Tuleap Git Branch SourceApplication · Jenkins
CVE-2022-43421
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 · uneditedA missing permission check in Jenkins Tuleap Git Branch Source Plugin 3.2.4 and earlier allows unauthenticated attackers to trigger Tuleap projects whose configured repository matches the attacker-specified value.
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 confidenceThe Tuleap Git Branch Source Plugin version 3.2.4 and earlier lacks proper permission checks in certain endpoints. This allows unauthenticated attackers to make API calls that trigger Tuleap project repository actions by specifying a repository value, potentially causing unauthorized CI/CD pipeline triggers or repository operations.
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
Tuleap Git Branch SourceApplication
< 3.2.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Tuleap Git Branch Source PluginNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Tuleap Git Branch Source' in the list of installed pluginsAffected if The plugin is present in the installed plugins list
-
Determine the installed plugin versionIn the plugin list, locate the 'Tuleap Git Branch Source' entry and note the version number displayed in the Version columnAffected if The version is 3.2.4 or earlier (any version below 3.2.5)
-
Verify the plugin is configured and activeCheck Jenkins jobs or folder configurations for any usage of the Tuleap Git Branch Source as a branch source, or check Manage Jenkins > Configure System for any Tuleap-related configurationAffected if The plugin is actively configured in any job or system settings, indicating it's in use
If the Tuleap Git Branch Source Plugin version is 3.2.4 or earlier and is installed or configured, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.5
Update Jenkins Tuleap Git Branch Source Plugin to version 3.2.5 or later, which includes the missing permission check. If immediate update is not possible, consider restricting network access to the Jenkins instance or disabling the plugin until patched.
3.2.5
- Navigate to Jenkins dashboard
- Go to Manage Jenkins > Manage Plugins
- Click on the Updates tab
- Locate the Tuleap Git Branch Source plugin
- Select the plugin and click Download now and install after restart
- Wait for the download to complete
- Restart Jenkins to apply the update
- Verify the plugin version is 3.2.5 or later in Installed plugins
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tuleap Git Branch Source
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43421 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43421 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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