pfSense 2.4.4-p3 diag_command.php csrf_callback txtCommand/txtRecallBuffer cross-site request forgery
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in pfSense 2.4.4-p3. It has been rated as problematic. This issue affects the function csrf_callback
of the file diag_command.php. The manipulation of the argument txtCommand/txtRecallBuffer leads to cross-site request forgery.
The identification of this vulnerability is CVE-2019-16667. The attack may be initiated remotely. There is no exploit available.
Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability was found in pfSense 2.4.4-p3 (Firewall Software). It has been declared as problematic. This vulnerability affects the function csrf_callback
of the file diag_command.php. The manipulation of the argument txtCommand/txtRecallBuffer
with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. CVE summarizes:
diag_command.php in pfSense 2.4.4-p3 allows CSRF via the txtCommand or txtRecallBuffer field, as demonstrated by executing OS commands. This occurs because csrf_callback() produces a "CSRF token expired" error and a Try Again button when a CSRF token is missing.
The weakness was presented 09/26/2019. This vulnerability was named CVE-2019-16667 since 09/21/2019. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
By approaching the search of inurl:diag_command.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.
See VDB-142381 and VDB-142380 for similar entries. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
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: 🔍
Timeline
09/21/2019 🔍09/26/2019 🔍
09/27/2019 🔍
12/28/2023 🔍
Sources
Advisory: 158614Status: Not defined
CVE: CVE-2019-16667 (🔍)
GCVE (CVE): GCVE-0-2019-16667
GCVE (VulDB): GCVE-100-142378
See also: 🔍
Entry
Created: 09/27/2019 06:04 PMUpdated: 12/28/2023 02:26 PM
Changes: 09/27/2019 06:04 PM (37), 09/10/2020 08:45 PM (18), 12/28/2023 02:26 PM (4)
Complete: 🔍
Cache ID: 18:F11:40
No comments yet. Languages: en.
Please log in to comment.