dbcve.org
FineractApplication · Apache

CVE-2018-1290

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Apache Fineract versions 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating, Using a single quotation escape with two continuous SQL parameters can cause a SQL injection. This could be done in Methods like retrieveAuditEntries of AuditsApiResource Class and retrieveCommands of MakercheckersApiResource Class.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Apache Fineract versions 1.0.0 through 0.4.0-incubating. The issue exists in retrieveAuditEntries (AuditsApiResource) and retrieveCommands (MakercheckersApiResource) methods where improper handling of single quotation escape with consecutive SQL parameters allows attackers to inject malicious SQL code.

MitigationReplace direct string concatenation in SQL queries with parameterized queries/prepared statements. Validate and properly escape all user-supplied input before incorporating it into SQL statements. Apply vendor patches or upgrade to a fixed version of Apache Fineract.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FineractApplication
Affected:= 0.4.0= 0.5.0= 0.6.0= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Apache Fineract version
    Check the version file or build configuration in your Fineract deployment (commonly found in version.properties, pom.xml, or the WAR file manifest)
    Affected if The installed version matches 0.4.0, 0.5.0, 0.6.0, or 1.0.0, or falls within the range 0.4.0-incubating through 1.0.0
  2. Verify AuditsApiResource is accessible
    Check if the /api/audits or similar audit API endpoint is exposed in your Fineract deployment configuration
    Affected if The audit API endpoint is accessible without additional authentication restrictions beyond standard API security
  3. Verify MakercheckersApiResource is accessible
    Check if the makerchecker API endpoint (typically /api/makercheckers or /api/commands) is exposed
    Affected if The makerchecker API endpoint is accessible and user input can be passed to the retrieveCommands method
  4. Identify if direct SQL parameter handling is in use
    Inspect the source code of AuditsApiResource.java and MakercheckersApiResource.java for string concatenation in SQL queries within retrieveAuditEntries and retrieveCommands methods
    Affected if The code uses direct string concatenation with user-supplied parameters in SQL queries rather than parameterized queries

You are affected if your Apache Fineract version is between 0.4.0-incubating and 1.0.0 (inclusive) and the audit or makerchecker API endpoints are accessible with user-controlled input reaching the vulnerable SQL query construction methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct string concatenation in SQL queries with parameterized queries/prepared statements. Validate and properly escape all user-supplied input before incorporating it into SQL statements. Apply vendor patches or upgrade to a fixed version of Apache Fineract.

Recommended fix Moderate confidence

1.0.1 or later

  1. Identify the current Apache Fineract version in your deployment (0.4.0, 0.5.0, 0.6.0, or 1.0.0)
  2. Backup your database and configuration files before proceeding with the upgrade
  3. Download Apache Fineract version 1.0.1 or later from the official Apache repository (archive.apache.org/dist/fineract/)
  4. Stop the Fineract services gracefully
  5. Upgrade the Fineract installation to version 1.0.1 or later by replacing the application binaries
  6. Review and update any custom configurations if required for compatibility with the new version
  7. Start the Fineract services and verify they start without errors
  8. Test the affected endpoints (retrieveAuditEntries in AuditsApiResource and retrieveCommands in MakercheckersApiResource) to confirm the SQL injection vulnerability is remediated
Caveat Minor point release; review release notes for any deprecated API endpoints or configuration changes, but no major breaking changes expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fineract Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1290 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data