CVE-2022-2647
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 · uneditedA vulnerability was found in jeecg-boot. It has been declared as critical. This vulnerability affects unknown code of the file /api/. 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. VDB-205594 is the identifier assigned to this vulnerability.
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 · moderate confidenceAn unrestricted file upload vulnerability exists in jeecg-boot's /api/ endpoint where the 'file' parameter can be manipulated to upload arbitrary files, potentially including malicious web shells. This allows remote attackers to achieve remote code execution on the server.
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 dataall versionsCVSS 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 if Jeecg Boot is installedReview your running applications, web server configs, or deployed artifacts for jeecg-boot or jeecg directories. Check process lists or container images for jeecg-related Java packages.Affected if Jeecg Boot is present in your environment
-
Confirm the /api/ endpoint is accessibleAttempt to reach the /api/ endpoint on your Jeecg Boot server (e.g., curl http://yourserver/api/ or check your reverse proxy/web server routing rules to see if /api/ paths are forwarded.Affected if The /api/ endpoint responds and accepts requests
-
Verify file upload functionality is exposedReview your application's API documentation or Swagger UI for endpoints that accept file uploads, particularly under /api/. Look for endpoints with 'upload' in the path or that accept multipart/form-data.Affected if A file upload endpoint exists and is reachable without authentication barriers
-
Check upload endpoint for allowlist validationInspect the source code of your file upload handler (look for classes handling multipart requests). Determine if the application validates file types using only client-side checks, or inspect the configuration for any allowlist settings.Affected if No server-side allowlist validation is enforced on uploaded file types, or only a loose allowlist exists
-
Confirm upload directory is web-accessibleCheck the application configuration or code for the upload directory path. Verify if uploaded files are stored within the web root (e.g., /static, /uploads, /webapp).Affected if Uploaded files are served from a directory accessible via HTTP/HTTPS
You are affected if Jeecg Boot is running with its /api/ file upload endpoint exposed and without strict server-side allowlist validation on file types.
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 dataRestrict file upload functionality by implementing strict allowlist-based file type validation, validating file content/magic bytes, storing uploads outside the web root, disabling script execution in upload directories, and renaming uploaded files.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2647 — 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-2647 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