Neo4j APOC up to 4.3.0.6/4.4.0.7 apoc.log.stream pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Neo4j APOC up to 4.3.0.6/4.4.0.7. This affects the function apoc.log.stream. This manipulation causes pathname traversal.
The identification of this vulnerability is CVE-2022-37423. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Neo4j APOC up to 4.3.0.6/4.4.0.7 and classified as critical. Affected by this vulnerability is the function apoc.log.stream. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Neo4j APOC (Awesome Procedures on Cypher) before 4.3.0.7 and 4.x before 4.4.0.8 allows Directory Traversal to sibling directories via apoc.log.stream.
The weakness was shared 08/12/2022 as GHSA-78f9-745f-278p. The advisory is shared at github.com. This vulnerability is known as CVE-2022-37423 since 08/05/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 4.3.0.7 or 4.4.0.8 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 4.3.0.0
- 4.3.0.1
- 4.3.0.2
- 4.3.0.3
- 4.3.0.4
- 4.3.0.5
- 4.3.0.6
- 4.4.0.0
- 4.4.0.1
- 4.4.0.2
- 4.4.0.3
- 4.4.0.4
- 4.4.0.5
- 4.4.0.6
- 4.4.0.7
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: Pathname traversalCWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: APOC 4.3.0.7/4.4.0.8
Timeline
08/05/2022 🔍08/12/2022 🔍
08/12/2022 🔍
09/11/2022 🔍
Sources
Advisory: GHSA-78f9-745f-278pStatus: Confirmed
CVE: CVE-2022-37423 (🔍)
GCVE (CVE): GCVE-0-2022-37423
GCVE (VulDB): GCVE-100-206329
Entry
Created: 08/12/2022 21:30Updated: 09/11/2022 07:39
Changes: 08/12/2022 21:30 (41), 09/11/2022 07:39 (11)
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.