dbcve.org
Kvf AdminApplication · Kvf Admin Project

CVE-2024-9280

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-27
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
A vulnerability has been found in kalvinGit kvf-admin up to f12a94dc1ebb7d1c51ee978a85e4c7ed75c620ff and classified as critical. This vulnerability affects the function fileUpload of the file FileUploadKit.java. The manipulation of the argument file leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

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

Unrestricted file upload vulnerability in kvf-admin's FileUploadKit.java allows remote attackers to upload arbitrary files via the fileUpload function without proper validation of file type, extension, or content. This can enable remote code execution if executable files are uploaded and accessed.

MitigationImplement strict file type validation using magic byte checks, whitelist allowed extensions, rename uploaded files, and store uploads outside the web root with proper content-disposition headers to prevent direct execution.

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
Kvf AdminApplication
Affected:= 2022-02-12

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.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 checks

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

  1. Identify if kvf-admin is deployed
    Search for the presence of 'kvf-admin' or 'FileUploadKit' in your application codebase, dependencies (pom.xml, build.gradle), or deployed JAR/WAR files.
    Affected if The kvf-admin component or FileUploadKit class is found in your environment
  2. Determine the installed Kvf Admin version
    Check your project version metadata: look in pom.xml, build.gradle, MANIFEST.MF, or the specific kvf-admin release artifact. The affected version is exactly '2022-02-12'.
    Affected if The installed version is exactly 2022-02-12 (this is a specific date-based version)
  3. Locate the FileUploadKit.java file
    Search for FileUploadKit.java in your source code or decompile the relevant class from deployed artifacts. Check for the fileUpload function method.
    Affected if The FileUploadKit.java file with the fileUpload function exists in your deployment
  4. Verify the upload endpoint is accessible
    Identify if the application's upload functionality is exposed via web endpoints. Check your routing/configuration for paths that invoke the fileUpload function (often /upload or similar patterns in the kvf-admin routing).
    Affected if The file upload endpoint is accessible from the web without authentication restrictions or the application uses the vulnerable FileUploadKit directly
  5. Check for file type validation in upload handling
    Inspect the FileUploadKit.java code or runtime behavior to determine if file extension, MIME type, or magic byte validation is performed before saving files.
    Affected if No file type, extension, or content validation is implemented in the upload handling logic

You are affected if you have kvf-admin version 2022-02-12 deployed with the FileUploadKit upload functionality exposed and no file validation in place.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation using magic byte checks, whitelist allowed extensions, rename uploaded files, and store uploads outside the web root with proper content-disposition headers to prevent direct execution.

Fix this in Kvf Admin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9280 — 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-2024-9280 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