CVE-2023-47467
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 · uneditedDirectory Traversal vulnerability in jeecg-boot v.3.6.0 allows a remote privileged attacker to obtain sensitive information via the file directory structure.
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 confidenceA directory traversal vulnerability in jeecg-boot v.3.6.0 allows authenticated privileged users to access files and directories outside the web root folder through manipulation of file path parameters, potentially exposing sensitive system configuration files, credentials, or application source code.
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= 3.6.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 the installed jeecg-boot versionLocate the version identifier in the application's configuration files, pom.xml, or application startup logs. Many Java applications expose version information in the manifest or welcome pages.Affected if The installed version is exactly 3.6.0
-
Verify if file upload or download features are enabledInspect the application codebase or configuration for file handling endpoints such as /upload, /download, /file, or similar REST controllers that accept file path parameters.Affected if File handling endpoints that accept path parameters exist and are accessible to the application
-
Confirm authentication is required for file operationsReview the application's security configuration to verify that file-related endpoints require valid authentication. Check if anonymous access is permitted on file handling routes.Affected if Authenticated users, including privileged users, can access the file handling functionality without additional restrictions
-
Check for path traversal protection on file operationsExamine the file handling code or proxy configurations for input validation that restricts file paths to intended directories. Look for path sanitization logic.Affected if The application does not validate or restrict file path parameters to prevent traversal outside the web root folder
-
Review application logs for suspicious file access patternsExamine access and application logs for requests with '../' sequences or attempts to access system directories such as /etc/, /windows/, or configuration files outside the web root.Affected if Such patterns are present in logs, indicating potential exploitation attempts or successful unauthorized access
A user is affected if they are running jeecg-boot version 3.6.0 and the application exposes file handling endpoints that accept path parameters without strict traversal protection.
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 dataUpgrade to a patched version of jeecg-boot if available; otherwise implement strict input validation and path sanitization on all file-handling endpoints, and ensure file access is restricted to intended directories via whitelisting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.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-2023-47467 — 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-2023-47467 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