CVE-2016-8750
CVE-2016-8750 is a medium-severity vulnerability in Apache Karaf with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-90.
Key facts
- Severity: Medium (CVSS 3.x base score 6.5)
- CVSS v2: 4.0
- EPSS exploit prediction: 5% (92nd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-90
- Affected product: Apache Karaf
- Published:
- Last modified:
Description
Apache Karaf prior to 4.0.8 used the LDAPLoginModule to authenticate users to a directory via LDAP. However, it did not encoding usernames properly and hence was vulnerable to LDAP injection attacks leading to a denial of service.
Frequently asked questions
- What is CVE-2016-8750?
- Apache Karaf prior to 4.0.8 used the LDAPLoginModule to authenticate users to a directory via LDAP. However, it did not encoding usernames properly and hence was vulnerable to LDAP injection attacks leading to a denial of service.
- How severe is CVE-2016-8750?
- CVE-2016-8750 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2016-8750 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (92nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2016-8750?
- CVE-2016-8750 affects Apache Karaf. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2016-8750?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2016-8750 published?
- CVE-2016-8750 was published on 2018-02-19 and last updated on 2026-06-17.
References
- http://www.securityfocus.com/bid/103098
- https://access.redhat.com/errata/RHSA-2018:1322
- https://karaf.apache.org/security/cve-2016-8750.txt
Affected products (1)
- cpe:2.3:a:apache:karaf:*:*:*:*:*:*:*:*
More vulnerabilities in Apache Karaf
- CVE-2022-40145 — Critical (CVSS 9.8): This vulnerable is about a potential code injection when an attacker has control of the target LDAP server using in the…
- CVE-2018-11788 — Critical (CVSS 9.8): Apache Karaf provides a features deployer, which allows users to "hot deploy" a features XML by dropping the file…
- CVE-2018-11786 — High (CVSS 8.8): In Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the…
- CVE-2021-41766 — High (CVSS 8.1): Apache Karaf allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX). JMX…
- CVE-2020-28052 — High (CVSS 8.1): An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility…
- CVE-2018-11787 — High (CVSS 8.1): In Apache Karaf version prior to 3.0.9, 4.0.9, 4.1.1, when the webconsole feature is installed in Karaf, it is…
All CVEs affecting Apache Karaf →
Other CWE-90 (LDAP Injection) vulnerabilities
- CVE-2026-44930 — Critical (CVSS 9.8): An LDAP injection vulnerability in the LDAP Certificate repository of the XKMS server in Apache CXF may allow an…
- CVE-2026-25560 — Critical (CVSS 9.8): WeKan versions prior to 8.19 contain an LDAP filter injection vulnerability in LDAP authentication. User-supplied…
- CVE-2024-54852 — Critical (CVSS 9.8): When LDAP connection is activated in Teedy versions between 1.9 to 1.12, the username field of the login form is…
- CVE-2024-33868 — Critical (CVSS 9.8): An issue was discovered in linqi before 1.4.0.1 on Windows. There is LDAP injection.
- CVE-2011-4069 — Critical (CVSS 9.8): html/admin/login.php in PacketFence before 3.0.2 allows remote attackers to conduct LDAP injection attacks and…
- CVE-2017-14596 — Critical (CVSS 9.8): In Joomla! before 3.8.0, inadequate escaping in the LDAP authentication plugin can result in a disclosure of a username…