Excellent Infotech BiYan up to 2.8 query_user.asp EMP_NO Password credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Excellent Infotech BiYan up to 2.8. It has been rated as problematic. This vulnerability affects unknown code of the file kws_login/asp/query_user.asp. Performing a manipulation of the argument EMP_NO results in credentials management (Password). This vulnerability is cataloged as CVE-2019-11232. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Excellent Infotech BiYan up to 2.8. It has been classified as problematic. This affects an unknown function of the file kws_login/asp/query_user.asp. The manipulation of the argument EMP_NO with an unknown input leads to a credentials management vulnerability (Password). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
EXCELLENT INFOTEK BiYan v1.57 ~ v2.8 allows an attacker to leak user information (Password) without being authenticated, by sending an EMP_NO element to the kws_login/asp/query_user.asp URI, and then reading the PWD element.
The weakness was shared 06/19/2019. This vulnerability is uniquely identified as CVE-2019-11232 since 04/15/2019. The exploitability is told to be easy. 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 T1552 for this issue.
By approaching the search of inurl:kws_login/asp/query_user.asp 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 entry VDB-136690 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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
Name: PasswordClass: Credentials management / Password
CWE: CWE-255
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
04/15/2019 🔍06/19/2019 🔍
06/20/2019 🔍
10/06/2023 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2019-11232 (🔍)
GCVE (CVE): GCVE-0-2019-11232
GCVE (VulDB): GCVE-100-136689
See also: 🔍
Entry
Created: 06/20/2019 08:00Updated: 10/06/2023 15:58
Changes: 06/20/2019 08:00 (39), 06/25/2020 20:12 (17), 10/06/2023 15:58 (3)
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.