CVE-2021-43782
Summary
| CVE | CVE-2021-43782 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-12-15 20:15:00 UTC |
| Updated | 2022-08-09 13:23:00 UTC |
| Description | Tuleap is a Libre and Open Source tool for end to end traceability of application and system developments. This is a follow up to GHSA-887w-pv2r-x8pm/CVE-2021-41276, the initial fix was incomplete. Tuleap does not sanitize properly the search filter built from the ldap_id attribute of a user during the daily synchronization. A malicious user could force accounts to be suspended or take over another account by forcing the update of the ldap_uid attribute. Note that the malicious user either need to have site administrator capability on the Tuleap instance or be an LDAP operator with the capability to create/modify account. The Tuleap instance needs to have the LDAP plugin activated and enabled for this issue to be exploitable. The following versions contain the fix: Tuleap Community Edition 13.2.99.83, Tuleap Enterprise Edition 13.1-6, and Tuleap Enterprise Edition 13.2-4. |
Risk And Classification
Problem Types: CWE-74
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Git - Tuleap | MISC | tuleap.net | |
| Indirect LDAP injection via the ldap_id attribute of a user · Advisory · Enalean/tuleap · GitHub | MISC | github.com | |
| Indirect LDAP injection via the ldap_id attribute of a user when - request #24168 - Requests - Tuleap | MISC | tuleap.net | |
| request #24168: Indirect LDAP injection via the ldap_id attribute of … · Enalean/tuleap@64e7756 · GitHub | MISC | github.com | |
| Indirect LDAP injection via the ldap_id attribute of a user when checking if it exists · Advisory · Enalean/tuleap · GitHub | CONFIRM | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.