dbcve.org
JimureportApplication · Jeecg

CVE-2023-6307

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-27
Fix available
A fix is available. Upgrade to after 1.6.1 or later.
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 classified as critical was found in jeecgboot JimuReport up to 1.6.1. Affected by this vulnerability is an unknown functionality of the file /download/image. The manipulation of the argument imageUrl leads to relative path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-246133 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

A path traversal vulnerability in JimuReport's /download/image endpoint allows remote attackers to manipulate the imageUrl parameter with relative path sequences (e.g., ../../../) to access arbitrary files on the server file system. With a CVSS 9.8 rating, this critical flaw can be exploited remotely without authentication.

MitigationUpgrade to a patched version of JimuReport beyond 1.6.1. If no upgrade is available, implement strict input validation on the imageUrl parameter to reject path traversal characters and normalize file paths before use.

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
JimureportApplication
Affected:<= 1.6.1

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 JimuReport installation
    Search for JimuReport web applications in your environment. Check for jimureport or jeecg-related directories, WAR files, or deployed applications on your application servers (Tomcat, Jetty, etc.). Review your web server logs for requests to /jimureport/ or similar paths.
    Affected if JimuReport is present in the environment
  2. Check installed JimuReport version
    Locate the JimuReport JAR or WAR file, typically named like jimureport-*.jar or jimureport.war. Inspect the manifest file (META-INF/MANIFEST.MF inside the JAR) or the application's pom.xml for the version attribute. Alternatively, check the version displayed in the admin UI if accessible.
    Affected if Version is 1.6.1 or lower
  3. Verify /download/image endpoint exposure
    Review your web server or reverse proxy configuration to determine if the JimuReport application is exposed externally. Check firewall rules and network ACLs. Test by attempting a curl or HTTP request to your application's /download/image endpoint.
    Affected if The endpoint is reachable from the network (internal or external) without authentication
  4. Confirm default configuration state
    Examine the application configuration files (typically in conf/ or config/ directories within the JimuReport deployment) for any security filters or path validation middleware that may be applied to the /download/image endpoint. Check if the application runs with default settings.
    Affected if No custom input validation filters are configured for the imageUrl parameter

The environment is affected if JimuReport version 1.6.1 or lower is installed and the /download/image endpoint is network-accessible, allowing an attacker to manipulate the imageUrl parameter with path traversal sequences.

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
Upgrade available Upgrade to a release after 1.6.1
Interim mitigation

Upgrade to a patched version of JimuReport beyond 1.6.1. If no upgrade is available, implement strict input validation on the imageUrl parameter to reject path traversal characters and normalize file paths before use.

Fix this in Jimureport Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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