FineractApplication · Apache
CVE-2022-44635
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 · uneditedApache Fineract allowed an authenticated user to perform remote code execution due to a path traversal vulnerability in a file upload component of Apache Fineract, allowing an attacker to run remote code. This issue affects Apache Fineract version 1.8.0 and prior versions. We recommend users to upgrade to 1.8.1.
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 confidenceApache Fineract contains a path traversal vulnerability in its file upload component. An authenticated attacker can manipulate file paths during upload to write files to arbitrary locations on the server, achieving remote code execution. The vulnerability affects version 1.8.0 and prior versions.
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
< 1.8.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Fineract versionLocate the Fineract version by checking the build configuration file (build.gradle), the application startup logs, or by querying the API endpoint that exposes version information (such as /api/v1/configuration or a dedicated about endpoint).Affected if The installed version is 1.8.0 or any prior version (anything below 1.8.1).
-
Verify file upload functionality is accessibleDetermine if the file upload API endpoints (typically under /api/v1/{entity}/upload or similar patterns involving multipart form data) are exposed and accessible to authenticated users within the application.Affected if File upload endpoints are enabled and reachable by authenticated users.
-
Check authentication configurationReview the authentication settings to confirm whether user authentication is required for file upload operations. Examine whether anonymous or low-privilege users can access upload functionality.Affected if Authenticated users (including potentially low-privilege users) can access file upload features.
-
Inspect upload path handlingExamine the file upload implementation to determine if user-supplied filename or path parameters are used without proper path sanitization. Look for evidence of path traversal patterns in upload requests.Affected if The upload mechanism allows manipulation of file paths through user-controlled input without validation.
You are affected if your Fineract installation is version 1.8.0 or earlier AND the file upload component is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.8.1
Upgrade Apache Fineract to version 1.8.1 or later. Additionally, implement strict input validation and path sanitization on all file upload functionality as a defense-in-depth measure.
1.8.1
- Review the official Apache Fineract 1.8.1 release notes and upgrade documentation for any specific migration requirements
- Create a complete backup of the existing Fineract database and configuration files
- Stop the currently running Fineract service
- Download Apache Fineract version 1.8.1 from the official Apache repository (https://fineract.apache.org/download/)
- Follow the standard Fineract upgrade procedure: replace the application binaries with version 1.8.1, ensure configuration files are compatible, and migrate any required data if specified in release notes
- Verify file permissions are correctly set on the new installation
- Restart the Fineract service
- Validate that the application is functioning correctly and the file upload functionality is working as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fineract
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44635 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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