Vulnerabilities > Netgate > Pfsense > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2014-07-02 | CVE-2014-4692 | Information Exposure vulnerability in Netgate Pfsense pfSense before 2.1.4, when HTTP is used, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie. | 4.3 |
| 2014-07-02 | CVE-2014-4691 | Remote Security vulnerability in Pfsense Session fixation vulnerability in pfSense before 2.1.4 allows remote attackers to hijack web sessions via a firewall login cookie. network netgate | 6.8 |
| 2014-07-02 | CVE-2014-4690 | Path Traversal vulnerability in Netgate Pfsense Multiple directory traversal vulnerabilities in pfSense before 2.1.4 allow (1) remote attackers to read arbitrary .info files via a crafted path in the pkg parameter to pkg_mgr_install.php and allow (2) remote authenticated users to read arbitrary files via the downloadbackup parameter to system_firmware_restorefullbackup.php. | 5.0 |
| 2014-07-02 | CVE-2014-4689 | Path Traversal vulnerability in Netgate Pfsense Absolute path traversal vulnerability in pkg_edit.php in pfSense before 2.1.4 allows remote attackers to read arbitrary XML files via a full pathname in the xml parameter. | 5.0 |
| 2014-07-02 | CVE-2014-4688 | Remote Security vulnerability in Pfsense pfSense before 2.1.4 allows remote authenticated users to execute arbitrary commands via (1) the hostname value to diag_dns.php in a Create Alias action, (2) the smartmonemail value to diag_smart.php, or (3) the database value to status_rrd_graph_img.php. | 6.5 |
| 2014-07-02 | CVE-2014-4687 | Cross-Site Scripting vulnerability in Netgate Pfsense Multiple cross-site scripting (XSS) vulnerabilities in pfSense before 2.1.4 allow remote attackers to inject arbitrary web script or HTML via (1) the starttime0 parameter to firewall_schedule.php, (2) the rssfeed parameter to rss.widget.php, (3) the servicestatusfilter parameter to services_status.widget.php, (4) the txtRecallBuffer parameter to exec.php, or (5) the HTTP Referer header to log.widget.php. | 4.3 |