StartTLS and SASL confidentiality protection bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Directory Studio | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Workaround
This issue was fixed in 2.0.0.v20210717-M17. All users using SASL are recommended to upgrade to Apache Directory Studio 2.0.0.v20210717-M17.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-1565 | While investigating DIRSTUDIO-1219 it was noticed that configured StartTLS encryption was not applied when any SASL authentication mechanism (DIGEST-MD5, GSSAPI) was used. While investigating DIRSTUDIO-1220 it was noticed that any configured SASL confidentiality layer was not applied. This issue affects Apache Directory Studio version 2.0.0.v20210213-M16 and prior versions. |
Github GHSA |
GHSA-4x25-f45x-grv5 | Missing encryption in Apache Directory Studio |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.793% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.