CVE-2019-12046 json
LemonLDAP::NG -2.0.3 has Incorrect Access Control.
published 7y ago modified 4mo ago also EUVD-2019-3700
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
LemonLDAP::NG -2.0.3 has Incorrect Access Control.
Patch / fix
- lemonldap-ng Debian 14, Debian 13, Debian 12 2.0.2+ds-7+deb10u1
debian advisories DEBIAN-CVE-2019-12046
Is CVE-2019-12046 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.13% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gitlab.ow2.org https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/issues/1742 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/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 |
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
gitlab.ow2.org
/lemonldap-ng/lemonldap-ng/issues/1742
exploit, third-party-advisory
-
lemonldap-ng.org
/download
product, vendor-advisory
-
gitlab.ow2.org
/lemonldap-ng/lemonldap-ng/commits/master
third-party-advisory
-
seclists.org
/bugtraq/2019/May/38
mailing-list, third-party-advisory
-
gitlab.ow2.org
/lemonldap-ng/lemonldap-ng/issues/1743
third-party-advisory
-
gitlab.ow2.org
/lemonldap-ng/lemonldap-ng/issues/1744
third-party-advisory
-
projects.ow2.org
/view/lemonldap-ng/lemonldap-ng-1-9-19-is-out/
release-notes, third-party-advisory
-
projects.ow2.org
/view/lemonldap-ng/lemonldap-ng-2-0-4-is-out/
release-notes, third-party-advisory
Sources
- CVE List CVE-2019-12046
- NVD CVE-2019-12046
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.