BlogoText up to 3.7.6 Access Restriction admin/preferences.php access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in BlogoText up to 3.7.6. This impacts an unknown function of the file admin/preferences.php of the component Access Restriction. Such manipulation leads to access control. This vulnerability is traded as CVE-2017-17794. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in BlogoText up to 3.7.6. It has been rated as critical. Affected by this issue is an unknown part of the file admin/preferences.php of the component Access Restriction. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:
validate_form_preferences in admin/preferences.php in BlogoText through 3.7.6 allows attackers to bypass intended access restrictions via vectors related to an e-mail address field.
The bug was discovered 11/17/2017. The weakness was shared 12/20/2017 (GitHub Repository). The advisory is available at github.com. This vulnerability is handled as CVE-2017-17794 since 12/20/2017. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 33 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin/preferences.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-110833 and VDB-110832 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
11/17/2017 🔍12/20/2017 🔍
12/20/2017 🔍
12/20/2017 🔍
12/20/2017 🔍
01/18/2023 🔍
Sources
Product: github.comAdvisory: 256041d8cab2fdc50678f4d49d916fea25cdb4fd
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-17794 (🔍)
GCVE (CVE): GCVE-0-2017-17794
GCVE (VulDB): GCVE-100-110834
See also: 🔍
Entry
Created: 12/20/2017 14:21Updated: 01/18/2023 13:32
Changes: 12/20/2017 14:21 (57), 12/16/2019 09:26 (2), 01/18/2023 13:32 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.