CVE-2019-16667

HIGHCVSS 8.8/10EPSS 54.54%

Last modified

CVE-2019-16667 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 54.54% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
8.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS Probability
54.54%

98.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
NetgatePfsense2.4.4P3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2019-16667?
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.
How severe is CVE-2019-16667?
CVE-2019-16667 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 54.54% probability of exploitation in the next 30 days.
How do I fix CVE-2019-16667?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2019-16667?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST