CVE-2024-35080
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 upload vulnerability in the gok4 method of inxedu v2024.4 allows attackers to execute arbitrary code via uploading a crafted .jsp file.
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 confidenceThis is an arbitrary file upload vulnerability in the 'gok4' method of inxedu v2024.4 that allows attackers to upload malicious .jsp (JavaServer Pages) files, which are executable on the Java application server, leading to remote code execution (RCE).
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= 2024.4CVSS 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 inxedu versionLocate the inxedu application and determine its installed version number. Check application metadata, build files, or version information in the deployment.Affected if version is exactly 2024.4
-
Locate the gok4 method or endpointSearch the application codebase or runtime for the 'gok4' method. This may appear as a URL endpoint, controller method, or API route.Affected if the gok4 method exists and is accessible in the application
-
Verify file upload functionality is presentInspect the application for file upload capabilities. Look for file upload forms, APIs, or handlers that accept user-submitted files.Affected if file upload functionality is enabled and accepts user files
-
Test for .jsp file upload acceptanceAttempt to upload a test .jsp file (or inspect the upload handler's validation logic) to see if .jsp extensions are allowed.Affected if .jsp file extensions are accepted by the upload mechanism without proper validation
-
Check uploaded file storage locationIdentify where uploaded files are stored on the filesystem. Determine if they reside within the web root or in a directory accessible via the web server.Affected if uploaded files are stored in a web-accessible directory where they can be executed
The environment is affected if running inxedu version 2024.4 with the gok4 method exposed and file upload functionality that permits .jsp files to be stored in a web-accessible location.
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 file upload validation to reject .jsp and other executable file extensions, validate file content/magic bytes rather than just extension, and store uploaded files outside the web root or in a non-executable location.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-35080 — 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-35080 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