| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Search Guard up to 23.0. Affected by this issue is some unknown functionality. This manipulation causes information disclosure (Hash). This vulnerability appears as CVE-2019-13421. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Search Guard up to 23.0. It has been declared as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a information disclosure vulnerability (Hash). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
Search Guard versions before 23.1 had an issue that an administrative user is able to retrieve bcrypt password hashes of other users configured in the internal user database.
The weakness was presented 08/23/2019 (Website). The advisory is shared at docs.search-guard.com. This vulnerability is known as CVE-2019-13421 since 07/08/2019. The exploitation appears to be easy. The attack can be launched remotely. Required for exploitation is a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 23.1 eliminates this vulnerability.
See VDB-139868 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.9
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: HashClass: Information disclosure / Hash
CWE: CWE-200 / CWE-284 / CWE-266
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: Search Guard 23.1
Timeline
07/08/2019 🔍08/23/2019 🔍
08/24/2019 🔍
08/04/2020 🔍
Sources
Advisory: docs.search-guard.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-13421 (🔍)
GCVE (CVE): GCVE-0-2019-13421
GCVE (VulDB): GCVE-100-140713
See also: 🔍
Entry
Created: 08/24/2019 10:53Updated: 08/04/2020 14:05
Changes: 08/24/2019 10:53 (56), 08/04/2020 14:05 (1)
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.