389-ds-base: ldapsearch with server side sort allows users to cause a crash
Published Sep 11, 2018
6.5
MEDIUMCVSS 3.1
EPSS 1.85%
Description
A flaw was found in the 389 Directory Server that allows users to cause a crash in the LDAP server using ldapsearch with server side sort.
Affected products
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||
|---|---|---|---|---|---|---|
| Red Hat | 389-DS-Base | n/a |
|
- ≥ 1.3.0.0 · < 1.3.8.7
- ≥ 1.4.0.0 · < 1.4.0.14
No data.
Red Hat Enterprise Linux 7
389-ds-base-0:1.3.7.5-28.el7_5
Fixed · RHSA-2018:2757
Red Hat Enterprise Linux 6
389-ds-base
Not affected
Red Hat Enterprise Linux 8
389-ds-base
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | 389-ds-base-0:1.3.7.5-28.el7_5 | Fixed | RHSA-2018:2757 |
| Red Hat Enterprise Linux 6 | 389-ds-base | Not affected | n/a |
| Red Hat Enterprise Linux 8 | 389-ds-base | Not affected | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
AV:N/AC:L/Au:S/C:N/I:N/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Table of values (13 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 1.85% (0.01847) | 78.30th | v5 (v2026.06.15) |
| Sep 20, 2026 | 1.85% (0.01847) | 78.12th | v5 (v2026.06.15) |
| Jul 20, 2024 | 1.79% (0.01785) | 88.26th | v3 (v2023.03.01) |
| Jun 26, 2024 | 1.79% (0.01785) | 88.18th | v3 (v2023.03.01) |
| Apr 30, 2024 | 2.45% (0.02454) | 89.88th | v3 (v2023.03.01) |
| Feb 2, 2024 | 3.44% (0.03437) | 90.59th | v3 (v2023.03.01) |
| Sep 5, 2023 | 4.79% (0.04789) | 91.69th | v3 (v2023.03.01) |
| Sep 3, 2023 | 4.98% (0.04978) | 91.82th | v3 (v2023.03.01) |
| Mar 7, 2023 | 4.49% (0.04491) | 91.16th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.95% (0.00950) | 32.28th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.95% (0.00950) | 13.46th | v2 (v2022.01.01) |
| Feb 3, 2022 | 1.04% (0.01040) | 28.32th | v5 (v2026.06.15) |
| Apr 14, 2021 | 1.04% (0.01040) | 0.00th | v1 |
References (8)
- http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00033.html vendor-advisoryx_refsource_SUSEMailing ListThird Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2757 vendor-advisoryx_refsource_REDHATThird Party Advisory
- https://access.redhat.com/security/cve/CVE-2018-10935 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1613606 Issue Tracking
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10935 x_refsource_CONFIRMIssue TrackingThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2018/08/msg00032.html mailing-listx_refsource_MLISTThird Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2018-10935
- https://www.cve.org/CVERecord?id=CVE-2018-10935
| Link | Providers | Tags |
|---|---|---|
| http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00033.html | vendor-advisoryx_refsource_SUSEMailing ListThird Party Advisory | |
| https://access.redhat.com/errata/RHSA-2018:2757 | vendor-advisoryx_refsource_REDHATThird Party Advisory | |
| https://access.redhat.com/security/cve/CVE-2018-10935 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1613606 | Issue Tracking | |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10935 | x_refsource_CONFIRMIssue TrackingThird Party Advisory | |
| https://lists.debian.org/debian-lts-announce/2018/08/msg00032.html | mailing-listx_refsource_MLISTThird Party Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2018-10935 | ||
| https://www.cve.org/CVERecord?id=CVE-2018-10935 |
Change history (0)
No recorded changes yet.