CVE-2023-33510: Jeecg p3 biz chat Jeecg P3 Biz Chat Allows Vulnerability
HIGHCVE-2023-33510 is a HIGH (CVSS 7.5) jeecg p3 biz chat allows vulnerability (CWE-668: Exposure of Resource to Wrong Sphere) affecting Jeecg p3 biz chat libraries in the Maven ecosystem. The issue involves jeecg p3 biz chat allows remote attackers to read arbitrary files. Remediation is available in the latest vendor maintenance releases.
CVE-2023-33510 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2023-33510
To remediate this vulnerability, upgrade all affected Jeecg p3 biz chat dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.jeecgframework.p3</groupId>
<artifactId>jeecg-p3-biz-chat</artifactId>
<version>Latest secure release</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.jeecgframework.p3
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2023-33510, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.jeecgframework.p3
Analyze the terminal output to locate any version of Jeecg p3 biz chat in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.jeecgframework.p3 command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-668: Exposure of Resource to Wrong Sphere, where the product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. In Jeecg p3 biz chat, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2023-33510 Affected Jeecg p3 biz chat Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.jeecgframework.p3:jeecg-p3-biz-chat
|
Maven |
≤ 1.0.5
|
|
References
Frequently Asked Questions
What is CVE-2023-33510?
Which Jeecg p3 biz chat versions are affected?
What version fixes CVE-2023-33510?
Is jeecg-p3-biz-chat affected?
What is the CVSS score of CVE-2023-33510?
What CWE is associated with CVE-2023-33510?
How can I check Maven dependencies for CVE-2023-33510?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-v3v9-3jf4-5pxx",
"modified" : "2023-06-16T17:55:54Z",
"published" : "2023-06-07T21:30:18Z",
"aliases" : [ "CVE-2023-33510" ],
"summary" : "Jeecg P3 Biz Chat allows remote attackers to read arbitrary files",
"details" : "Jeecg P3 Biz Chat 1.0.5 allows remote attackers to read arbitrary files through specific parameters.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.jeecgframework.p3:jeecg-p3-biz-chat"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.0.5"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-33510"
}, {
"type" : "WEB",
"url" : "https://carl1l.github.io/2023/05/08/jeecg-p3-biz-chat-1-0-5-jar-has-arbitrary-file-read-vulnerability"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-668" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2023-06-09T22:54:03Z",
"nvd_published_at" : "2023-06-07T20:15:09Z"
}
}