baigoStudio baigoSSO 3.0.1 Configuration Screen opt_base.inc.php BG_SITE_NAME input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in baigoStudio baigoSSO 3.0.1. Impacted is an unknown function of the file opt_base.inc.php of the component Configuration Screen. Executing a manipulation of the argument BG_SITE_NAME can lead to input validation. This vulnerability appears as CVE-2019-10015. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as critical was found in baigoStudio baigoSSO 3.0.1. This vulnerability affects some unknown functionality of the file opt_base.inc.php of the component Configuration Screen. The manipulation of the argument BG_SITE_NAME with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
baigoStudio baigoSSO v3.0.1 allows remote attackers to execute arbitrary PHP code via the first form field of a configuration screen, because this code is written to the BG_SITE_NAME field in the opt_base.inc.php file.
The bug was discovered 03/06/2019. The weakness was presented 03/24/2019. This vulnerability was named CVE-2019-10015 since 03/24/2019. The exploitation appears to be easy. The attack can be initiated remotely. A single authentication is required for exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 18 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:opt_base.inc.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.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: Input validationCWE: CWE-20
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: 🔍
Timeline
03/06/2019 🔍03/24/2019 🔍
03/24/2019 🔍
03/25/2019 🔍
08/04/2023 🔍
Sources
Product: github.comAdvisory: 12
Status: Not defined
CVE: CVE-2019-10015 (🔍)
GCVE (CVE): GCVE-0-2019-10015
GCVE (VulDB): GCVE-100-132148
Entry
Created: 03/25/2019 06:59Updated: 08/04/2023 18:10
Changes: 03/25/2019 06:59 (55), 05/19/2020 15:37 (1), 08/04/2023 18:10 (4)
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.