dbcve.org
TuleapApplication · Enalean

CVE-2025-24029

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to 16.2-7 / 16.3-5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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
Tuleap is an Open Source Suite to improve management of software developments and collaboration. Users (possibly anonymous ones if the widget is used in the dashboard of a public project) might get access to artifacts they should not see. This issue has been addressed in Tuleap Community Edition 16.3.99.1737562605 as well as Tuleap Enterprise Edition 16.3-5 and Tuleap Enterprise Edition 16.2-7. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

A detailed technical summary for this CVE is being prepared.

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
TuleapApplication
Affected:< 16.2-7< 16.3.99.1737562605>= 16.3, < 16.3-5

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

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

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 16.2-7 / 16.3-5 / 16.3.99.1737562605 or later
Fixed in 16.2-716.3-516.3.99.1737562605
Vendor patch github.com →
Recommended fix High confidence

Tuleap Enterprise Edition 16.2-7 / 16.3-5 or Tuleap Community Edition 16.3.99.1737562605

  1. Identify your current Tuleap version by checking the Tuleap about page or using CLI tools
  2. Determine which edition (Community or Enterprise) and branch (16.2.x or 16.3.x) you are running
  3. For Tuleap Enterprise Edition 16.2.x users: Upgrade to version 16.2-7 or later
  4. For Tuleap Enterprise Edition 16.3.x users: Upgrade to version 16.3-5 or later
  5. For Tuleap Community Edition users: Upgrade to version 16.3.99.1737562605 or later
  6. Follow the standard Tuleap upgrade documentation for your installation method (DEB, RPM, or Docker)
  7. After upgrade, verify the Tuleap version matches the fixed release
  8. Test that artifact permissions are correctly enforced for users across different project access levels

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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