Skip to content
Fencer Intel
high 8.1

CVE-2021-41232 json

Improper Neutralization of Special Elements used in an LDAP Query

published 5y ago modified 4mo ago also GHSA-26cm-qrc6-mfgj , GO-2022-0939 , EUVD-2021-2275

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

Thunderdome is an open source agile planning poker tool in the theme of Battling for points. In affected versions there is an LDAP injection vulnerability which affects instances with LDAP authentication enabled. The provided username is not properly escaped. This issue has been patched in version 1.16.3. If users are unable to update they should disable the LDAP feature if in use.

Patch / fix

  • go github.com/stevenweathers/thunderdome-planning-poker 1.16.3
  • go github.com/StevenWeathers/thunderdome-planning-poker 1.16.3
  • thunderdome planning_poker 1.16.3

Is CVE-2021-41232 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/stevenweathers/thunderdome-planning-poker
<1.16.3
1.16.3
go github.com/StevenWeathers/thunderdome-planning-poker
<1.16.3
1.16.3

Affected products

  • StevenWeathers thunderdome-planning-poker

Classification

Weakness
  • CWE-90 Improper Neutralization of Special Elements used in an LDAP Query
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
  • CWE-116 Improper Encoding or Escaping of Output

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.