RuvarOA 6.01/12.01 SearchCondiction.aspx PageID sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in RuvarOA 6.01/12.01 and classified as critical. This issue affects some unknown processing of the file /WebUtility/SearchCondiction.aspx. The manipulation of the argument PageID leads to sql injection. The identification of this vulnerability is CVE-2024-25531. The attack may be initiated remotely. There is no exploit available. Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability has been found in RuvarOA 6.01/12.01 and classified as critical. This vulnerability affects an unknown function of the file /WebUtility/SearchCondiction.aspx. The manipulation of the argument PageID
with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the PageID parameter at /WebUtility/SearchCondiction.aspx.
The advisory is available at gist.github.com. This vulnerability was named CVE-2024-25531 since 02/07/2024. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/08/2024). This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
By approaching the search of inurl:WebUtility/SearchCondiction.aspx 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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
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
02/07/2024 🔍05/08/2024 🔍
05/08/2024 🔍
05/08/2024 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2024-25531 (🔍)
GCVE (CVE): GCVE-0-2024-25531
GCVE (VulDB): GCVE-100-263578
Entry
Created: 05/08/2024 06:11 PMChanges: 05/08/2024 06:11 PM (52)
Complete: 🔍
Cache ID: 18:309:40
No comments yet. Languages: en.
Please log in to comment.