| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Groovy LDAP API. This vulnerability affects unknown code of the file main/java/org/apache/directory/groovyldap/LDAP.java. Performing a manipulation of the argument returnObjFlag results in 7pk security (Poison). This vulnerability is known as CVE-2016-6497. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Groovy LDAP API (Directory Service Software) (the affected version is unknown). It has been classified as critical. This affects an unknown code of the file main/java/org/apache/directory/groovyldap/LDAP.java. The manipulation of the argument returnObjFlag with an unknown input leads to a 7pk security vulnerability (Poison). CWE is classifying the issue as CWE-254. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
main/java/org/apache/directory/groovyldap/LDAP.java in the Groovy LDAP API allows attackers to conduct LDAP entry poisoning attacks by leveraging setting returnObjFlag to true for all search methods.
The bug was discovered 01/18/2017. The weakness was published 01/18/2017 by Alex (Website). The advisory is shared at svn.apache.org. This vulnerability is uniquely identified as CVE-2016-6497 since 08/01/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1211 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95929†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: PoisonClass: 7pk security / Poison
CWE: CWE-254
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/01/2016 🔍01/18/2017 🔍
01/18/2017 🔍
01/18/2017 🔍
01/19/2017 🔍
02/01/2017 🔍
07/24/2020 🔍
Sources
Advisory: svn.apache.orgResearcher: Alex
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-6497 (🔍)
GCVE (CVE): GCVE-0-2016-6497
GCVE (VulDB): GCVE-100-95505
SecurityFocus: 95929 - Apache Groovy CVE-2016-6497 Information Disclosure Vulnerability
OSVDB: - CVE-2016-6497 - Apache - Groovy LDAP - LDAP Poisoning Issue
Entry
Created: 01/19/2017 09:44Updated: 07/24/2020 16:47
Changes: 01/19/2017 09:44 (58), 07/24/2020 16:47 (7)
Complete: 🔍
Cache ID: 216:AD6: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.