Apache Karaf up to 4.0.7 LDAPLoginModule Username LDAP injection ldap injection

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Apache Karaf up to 4.0.7. Impacted is an unknown function of the component LDAPLoginModule. This manipulation of the argument Username causes ldap injection (LDAP injection). The identification of this vulnerability is CVE-2016-8750. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Apache Karaf up to 4.0.7. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component LDAPLoginModule. The manipulation of the argument username with an unknown input leads to a ldap injection vulnerability (LDAP injection). The CWE definition for the vulnerability is CWE-90. The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component. As an impact it is known to affect availability. The summary by CVE is:
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.
The bug was discovered 02/19/2018. The weakness was shared 02/19/2018 (Website). The advisory is shared at karaf.apache.org. This vulnerability is known as CVE-2016-8750 since 10/18/2016. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation needs a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 4.0.8 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103098†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: LDAP injectionClass: Ldap injection / LDAP injection
CWE: CWE-90 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Karaf 4.0.8
Timeline
10/18/2016 🔍02/19/2018 🔍
02/19/2018 🔍
02/19/2018 🔍
02/19/2018 🔍
02/20/2018 🔍
02/08/2023 🔍
Sources
Vendor: apache.orgAdvisory: RHSA-2018:1322
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-8750 (🔍)
GCVE (CVE): GCVE-0-2016-8750
GCVE (VulDB): GCVE-100-113569
SecurityFocus: 103098 - Apache Karaf CVE-2016-8750 LDAP Injection Vulnerability
Entry
Created: 02/20/2018 08:08Updated: 02/08/2023 13:17
Changes: 02/20/2018 08:08 (61), 01/06/2020 17:25 (4), 02/08/2023 13:17 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.