Date
|
ID
|
Source Package(s)
|
Type
|
Affected release(s)
|
CVE
|
2022-11-08
|
MGASA-2022-0413 |
389-ds-base
|
security |
8
|
CVE-2022-2850
|
2022-06-24
|
MGASA-2022-0239 |
389-ds-base
|
security |
8
|
CVE-2022-1949
|
2022-04-09
|
MGASA-2022-0134 |
389-ds-base
|
security |
8
|
CVE-2022-0918
,
CVE-2022-0996
|
2022-03-21
|
MGASA-2022-0106 |
389-ds-base
|
security |
8
|
CVE-2021-4091
|
2021-09-23
|
MGASA-2021-0440 |
389-ds-base
|
security |
8
|
CVE-2021-3652
|
2019-12-25
|
MGASA-2019-0411 |
389-ds-base
|
security |
7
|
CVE-2018-1054
,
CVE-2018-10871
,
CVE-2019-3883
,
CVE-2019-14824
|
2018-11-20
|
MGASA-2018-0461 |
389-ds-base
|
security |
6
|
CVE-2018-14648
|
2018-10-19
|
MGASA-2018-0404 |
389-ds-base
|
security |
6
|
CVE-2018-10850
,
CVE-2018-10935
,
CVE-2018-14624
|
2018-05-16
|
MGASA-2018-0245 |
389-ds-base
|
security |
6
|
CVE-2018-1089
|
2018-04-06
|
MGASA-2018-0193 |
389-ds-base
|
security |
6
|
CVE-2017-15135
|
2018-03-07
|
MGASA-2018-0162 |
389-ds-base
|
security |
6
|
CVE-2018-1054
|
2018-02-08
|
MGASA-2018-0122 |
389-ds-base
|
security |
6
|
CVE-2017-15134
|
2017-09-16
|
MGASA-2017-0340 |
389-ds-base
|
security |
6
,
5
|
CVE-2017-7551
|
2017-05-02
|
MGASA-2017-0123 |
389-ds-base
|
security |
5
|
CVE-2017-2668
|
2017-01-27
|
MGASA-2017-0028 |
389-ds-base
|
security |
5
|
CVE-2017-2591
|
2016-10-21
|
MGASA-2016-0350 |
389-ds-base
|
security |
5
|
CVE-2016-4992
|
2016-02-23
|
MGASA-2016-0081 |
389-ds-base
|
security |
5
|
CVE-2016-0741
|
2015-10-15
|
MGASA-2015-0402 |
389-ds-base
|
security |
5
|
CVE-2015-3230
|
2015-05-03
|
MGASA-2015-0183 |
389-ds-base
|
security |
4
|
CVE-2015-1854
|
2015-03-14
|
MGASA-2015-0108 |
389-ds-base
|
security |
4
|
CVE-2014-8105
,
CVE-2014-8112
|
2014-08-18
|
MGASA-2014-0333 |
389-ds-base
|
security |
4
,
3
|
CVE-2014-3562
|
2014-03-31
|
MGASA-2014-0145 |
389-ds-base
|
security |
4
,
3
|
CVE-2014-0132
|
2013-11-30
|
MGASA-2013-0357 |
389-ds-base
|
security |
3
|
CVE-2013-4485
|
2013-08-30
|
MGASA-2013-0263 |
389-ds-base
|
security |
3
|
CVE-2013-2219
,
CVE-2013-4283
|