CVE-2024-24024
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 · uneditedAn arbitrary File download vulnerability exists in Novel-Plus v4.3.0-RC1 and prior at com.java2nb.common.controller.FileController: fileDownload(). An attacker can pass in specially crafted filePath and fieName parameters to perform arbitrary File download.
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 confidenceNovel-Plus v4.3.0-RC1 and prior contains an arbitrary file download vulnerability in the FileController.fileDownload() method. The method accepts filePath and fileName parameters without proper validation, allowing attackers to use path traversal sequences (e.g., ../../../) to access and download sensitive files from the server filesystem outside the intended directory.
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<= 4.2.0= 4.3.0CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Novel-Plus versionLocate the version manifest or build file in the deployment (such as pom.xml, version.properties, or the application startup banner) and note the exact version numberAffected if The version is 4.2.0 or lower, or exactly 4.3.0 (including 4.3.0-RC1)
-
Verify FileController is deployedLocate the FileController.java class in the deployed application source or decompiled bytecode and confirm the fileDownload() method existsAffected if The FileController class with fileDownload() method is present in the application
-
Confirm file download endpoint is accessibleCheck the web application routing configuration (such as @RequestMapping annotations in FileController or the deployed URL patterns) to determine if the /file/download or equivalent endpoint is publicly or internally accessibleAffected if The file download endpoint is exposed without authentication or additional access controls
-
Check for path traversal protection in fileDownload()Review the fileDownload() method implementation to see if it validates that the requested file stays within an allowed directory (look for path sanitization, canonical path checks, or allow-list validation)Affected if The method accepts filePath or fileName parameters without validating them against path traversal sequences (../) or without enforcing directory confinement
-
Test for path traversal vulnerabilityIf authorized, send a request to the file download endpoint with a filePath parameter containing ../ sequences (e.g., ../../../etc/passwd) to see if files outside the intended directory are returnedAffected if The application returns files from outside the intended upload/download directory when using path traversal sequences
You are affected if you are running Novel-Plus version 4.2.0 or lower, or version 4.3.0 (including RC1), and the fileDownload() endpoint is accessible without proper path traversal validation.
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.
From vendor dataImplement strict input validation and path sanitization in the fileDownload() method to ensure requested files are confined within an allowed base directory. Use canonical path resolution and explicit allow-listing of accessible directories before serving files.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24024 — 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-2024-24024 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