pfSense up to 2.4.4-p3 picture.widget.php file_get_contents/file_put_contents widgetkey input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in pfSense up to 2.4.4-p3. This affects the function file_get_contents/file_put_contents of the file widgets/widgets/picture.widget.php. This manipulation of the argument widgetkey as part of Parameter causes input validation.
This vulnerability is handled as CVE-2019-16915. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in pfSense up to 2.4.4-p3 (Firewall Software). Affected by this vulnerability is the function file_get_contents/file_put_contents of the file widgets/widgets/picture.widget.php. The manipulation of the argument widgetkey as part of a Parameter leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in pfSense through 2.4.4-p3. widgets/widgets/picture.widget.php uses the widgetkey parameter directly without sanitization (e.g., a basename call) for a pathname to file_get_contents or file_put_contents.
The weakness was released 09/26/2019. This vulnerability is known as CVE-2019-16915 since 09/26/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
By approaching the search of inurl:widgets/widgets/picture.widget.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.
Entries connected to this vulnerability are available at VDB-142380 and VDB-142378. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://github.com/pfsense/pfsense/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Input validationCWE: CWE-20
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: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
09/26/2019 🔍09/26/2019 🔍
09/27/2019 🔍
12/28/2023 🔍
Sources
Product: github.comAdvisory: 2c544ac61ce98f716d50b8e5961d7dfba66804b5
Status: Not defined
CVE: CVE-2019-16915 (🔍)
GCVE (CVE): GCVE-0-2019-16915
GCVE (VulDB): GCVE-100-142381
See also: 🔍
Entry
Created: 09/27/2019 18:05Updated: 12/28/2023 14:34
Changes: 09/27/2019 18:05 (38), 09/10/2020 21:04 (18), 12/28/2023 14:34 (5)
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.