Codextrous B2J Contact Extension up to 2.1.12 on Joomla uniqid path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Codextrous B2J Contact Extension up to 2.1.12 on Joomla. It has been rated as problematic. This impacts an unknown function of the component uniqid Handler. Performing a manipulation results in path traversal. This vulnerability is identified as CVE-2017-9030. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Codextrous B2J Contact Extension up to 2.1.12 on Joomla (Joomla Component). This affects an unknown function of the component uniqid Handler. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality. The summary by CVE is:
The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a directory traversal attack that bypasses a uniqid protection mechanism, and makes it easier to read arbitrary uploaded files.
The bug was discovered 12/27/2016. The weakness was released 05/17/2017 (Website). It is possible to read the advisory at navixia.com. This vulnerability is uniquely identified as CVE-2017-9030 since 05/17/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 141 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.1.13 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-101441 and VDB-101442. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Path traversalCWE: 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: B2J Contact Extension 2.1.13
Timeline
12/27/2016 🔍05/17/2017 🔍
05/17/2017 🔍
05/17/2017 🔍
05/18/2017 🔍
06/26/2020 🔍
Sources
Advisory: navixia.comStatus: Not defined
CVE: CVE-2017-9030 (🔍)
GCVE (CVE): GCVE-0-2017-9030
GCVE (VulDB): GCVE-100-101451
See also: 🔍
Entry
Created: 05/18/2017 16:35Updated: 06/26/2020 17:59
Changes: 05/18/2017 16:35 (62), 06/26/2020 17:59 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.