CVE-2022-41852
VMware Unknown/Unclassified
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
INFO
Published Date :
Oct. 6, 2022, 6:17 p.m.
Last Modified :
Nov. 7, 2023, 3:53 a.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
Public PoC/Exploit Available at Github
CVE-2022-41852 has a 7 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
Affected Products
The following products are affected by CVE-2022-41852
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
None
Java
None
None
Java CVE Vulnerability Environment
cve java dubbo apache spring
Java HTML PLpgSQL Python JavaScript CSS Shell Dockerfile
CVE-2022-41852 Proof of Concept (unofficial)
cve hacking penetration-testing pentesting proof-of-concept rce remote-code-execution security vulnerability cve-2022-41852 jxpath
Java
一个java代码审计辅助工具
Java JavaScript HTML
a rep for documenting my study, may be from 0 to 0.1
Java Dockerfile Shell Python HTML
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-41852 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-41852 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Source Update by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Changed Source Google Inc. Apache Software Foundation -
CVE Modified by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Changed Description ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. -
CVE Modified by [email protected]
Nov. 21, 2022
Action Type Old Value New Value Changed Description ** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google in breach of the CNA rules. After review by the JXPath maintainers, the original report was found to be invalid. ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. Removed Reference https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47133 [Exploit, Issue Tracking, Third Party Advisory] Removed CWE Google Inc. CWE-470 -
CVE Rejected by [email protected]
Nov. 21, 2022
Action Type Old Value New Value -
CVE Modified by [email protected]
Nov. 10, 2022
Action Type Old Value New Value Changed Description Those using JXPath to interpret untrusted XPath expressions may be vulnerable to a remote code execution attack. All JXPathContext class functions processing a XPath string are vulnerable except compile() and compilePath() function. The XPath expression can be used by an attacker to load any Java class from the classpath resulting in code execution. ** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google in breach of the CNA rules. After review by the JXPath maintainers, the original report was found to be invalid. Removed CVSS V3.1 Google Inc. AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H Removed CVSS V3.1 Reason I-No limiting factors Removed CVSS V3.1 Reason S-Unclear if Scope change occurs Removed CVSS V3.1 Reason C-No limiting factors Removed CVSS V3.1 Reason PR-No privileges needed -
Initial Analysis by [email protected]
Oct. 07, 2022
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47133 No Types Assigned https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47133 Exploit, Issue Tracking, Third Party Advisory Added CWE NIST CWE-470 Added CPE Configuration OR *cpe:2.3:a:apache:commons_jxpath:*:*:*:*:*:*:*:* versions up to (including) 1.3
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-41852 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-41852
weaknesses.