zzcms 8.2 ErrorCase.class.php Request Path path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in zzcms 8.2. This issue affects some unknown processing of the file 3/qq_connect2.0/API/class/ErrorCase.class.php. The manipulation as part of Request leads to path traversal (Path). This vulnerability is uniquely identified as CVE-2018-7434. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in zzcms 8.2 (Content Management System). It has been rated as problematic. This issue affects some unknown processing of the file 3/qq_connect2.0/API/class/ErrorCase.class.php. The manipulation as part of a Request leads to a path traversal vulnerability (Path). Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:
zzcms 8.2 allows remote attackers to discover the full path via a direct request to 3/qq_connect2.0/API/class/ErrorCase.class.php or 3/ucenter_api/code/friend.php.
The bug was discovered 02/24/2018. The weakness was disclosed 02/24/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-7434 since 02/23/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
By approaching the search of inurl:3/qq_connect2.0/API/class/ErrorCase.class.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: PathClass: Path traversal / Path
CWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
02/23/2018 🔍02/23/2018 🔍
02/24/2018 🔍
02/24/2018 🔍
02/24/2018 🔍
01/08/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-7434 (🔍)
GCVE (CVE): GCVE-0-2018-7434
GCVE (VulDB): GCVE-100-113777
Entry
Created: 02/24/2018 09:07Updated: 01/08/2020 11:45
Changes: 02/24/2018 09:07 (58), 01/08/2020 11:45 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.