ShowDoc AdminSettingController.class.php getLoginSecretKey cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in ShowDoc. The affected element is the function getLoginSecretKey of the file server/Application/Api/Controller/AdminSettingController.class.php. Executing a manipulation can lead to cryptographic issue.
This vulnerability is handled as CVE-2021-3680. It is possible to launch the attack on the local host. There is not any exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability has been found in ShowDoc (affected version unknown) and classified as problematic. This vulnerability affects the function getLoginSecretKey of the file server/Application/Api/Controller/AdminSettingController.class.php. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect confidentiality.
The weakness was released 08/04/2021. The advisory is shared for download at huntr.dev. This vulnerability was named CVE-2021-3680. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1600.
By approaching the search of inurl:server/Application/Api/Controller/AdminSettingController.class.php it is possible to find vulnerable targets with Google Hacking.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.5VulDB Meta Temp Score: 2.4
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Cryptographic issueCWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
08/03/2021 🔍08/04/2021 🔍
08/04/2021 🔍
08/08/2021 🔍
Sources
Advisory: huntr.devStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-3680 (🔍)
GCVE (CVE): GCVE-0-2021-3680
GCVE (VulDB): GCVE-100-180076
Entry
Created: 08/04/2021 20:07Updated: 08/08/2021 08:10
Changes: 08/04/2021 20:07 (37), 08/08/2021 08:09 (3), 08/08/2021 08:10 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.