VDB-116929 · CVE-2018-1292 · BID 104007

Apache Fineract getReportType reportName sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Apache Fineract 0.4.0-incubating/0.5.0-incubating/0.6.0-incubating/1.0.0. Affected is the function getReportType. This manipulation of the argument reportName as part of Parameter causes sql injection. The identification of this vulnerability is CVE-2018-1292. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as critical was found in Apache Fineract 0.4.0-incubating/0.5.0-incubating/0.6.0-incubating/1.0.0. Affected by this vulnerability is the function getReportType. The manipulation of the argument reportName as part of a Parameter 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:

Within the 'getReportType' method in Apache Fineract 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, a hacker could inject SQL to read/update data for which he doesn't have authorization for by way of the 'reportName' parameter.

The bug was discovered 04/19/2018. The weakness was shared 04/20/2018 (Website). The advisory is shared at lists.apache.org. This vulnerability is known as CVE-2018-1292 since 12/07/2017. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation needs a single authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/30/2020). MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 104007†). The entries VDB-116928, VDB-116927 and VDB-116926 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.2
VulDB Meta Temp Score: 7.2

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.1
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/07/2017 🔍
04/19/2018 +133 days 🔍
04/19/2018 +0 days 🔍
04/20/2018 +0 days 🔍
04/20/2018 +0 days 🔍
04/21/2018 +1 days 🔍
01/30/2020 +649 days 🔍

Sourcesinfo

Vendor: apache.org

Advisory: lists.apache.org
Status: Not defined

CVE: CVE-2018-1292 (🔍)
GCVE (CVE): GCVE-0-2018-1292
GCVE (VulDB): GCVE-100-116929
SecurityFocus: 104007 - Apache Fineract CVE-2018-1292 SQL Injection Vulnerability

See also: 🔍

Entryinfo

Created: 04/21/2018 18:51
Updated: 01/30/2020 11:40
Changes: 04/21/2018 18:51 (61), 01/30/2020 11:40 (3)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!