| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Fidelix FX-20. The impacted element is an unknown function. The manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2016-9364. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in Fidelix FX-20 and classified as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a path traversal vulnerability. 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, and integrity. The summary by CVE is:
An issue was discovered in Fidelix FX-20 series controllers, versions prior to 11.50.19. Arbitrary file reading via path traversal allows an attacker to access arbitrary files and directories on the server.
The bug was discovered 12/22/2016. The weakness was disclosed 02/13/2017 with Positive Technologies (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2016-9364 since 11/16/2016. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 53 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 11.50.19 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95073†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.8
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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: FX-20 11.50.19
Timeline
11/16/2016 🔍12/22/2016 🔍
12/22/2016 🔍
02/13/2017 🔍
02/13/2017 🔍
02/14/2017 🔍
08/14/2020 🔍
Sources
Advisory: securityfocus.com⛔Organization: Positive Technologies
Status: Not defined
CVE: CVE-2016-9364 (🔍)
GCVE (CVE): GCVE-0-2016-9364
GCVE (VulDB): GCVE-100-96917
SecurityFocus: 95073 - Fidelix FX-20 Series Controllers CVE-2016-9364 Directory Traversal Vulnerability
OSVDB: - CVE-2016-9364 - Fidelix - FX-20 - Directory Traversal Issue
Entry
Created: 02/14/2017 09:16Updated: 08/14/2020 14:36
Changes: 02/14/2017 09:16 (57), 08/14/2020 14:36 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.