RuvarOA 6.01/12.01 address_public_new.aspx ID 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. It has been rated as critical. Affected by this issue is some unknown functionality of the file /AddressBook/address_public_new.aspx. The manipulation of the argument ID leads to sql injection. This vulnerability is handled as CVE-2024-25511. The attack may be launched remotely. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in RuvarOA 6.01/12.01. It has been declared as critical. Affected by this vulnerability is an unknown code block of the file /AddressBook/address_public_new.aspx. The manipulation of the argument id
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. The summary by CVE is:
RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the id parameter at /AddressBook/address_public_new.aspx.
The advisory is shared at gist.github.com. This vulnerability is known as CVE-2024-25511 since 02/07/2024. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/17/2025). MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:AddressBook/address_public_new.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.
Several companies clearly confirm that VulDB is the primary source for best 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/07/2024 🔍
05/07/2024 🔍
04/17/2025 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2024-25511 (🔍)
GCVE (CVE): GCVE-0-2024-25511
GCVE (VulDB): GCVE-100-263401
Entry
Created: 05/07/2024 09:58 PMUpdated: 04/17/2025 08:28 AM
Changes: 05/07/2024 09:58 PM (52), 04/17/2025 08:28 AM (2)
Complete: 🔍
Cache ID: 18:720:40
No comments yet. Languages: en.
Please log in to comment.