IPCop is a Linux-based firewall and network gateway appliance that presents a narrow vulnerability footprint centered on its core product. The observed weakness classes span web-tier input handling, including cross-site scripting and command injection, typical of network administration interfaces exposed to trusted networks. Current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Ipcop over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2004-1210MEDIUM Cross-site scripting (XSS) vulnerability in proxylog.dat in IPCop 1.4.1 and possibly other versions, allows remote attackers to inject arbitrary web script or HTML via the (1) url | Jan 10, 2005 | 6.8 | 32 | NO | YES |
CVE-2013-7418MEDIUM cgi-bin/iptablesgui.cgi in IPCop (aka IPCop Firewall) before 2.1.5 allows remote authenticated users to execute arbitrary code via shell metacharacters in the TABLE parameter. NOT | Jan 2, 2015 | 6.5 | 23 | NO | NO |
CVE-2013-7417MEDIUM Cross-site scripting (XSS) vulnerability in cgi-bin/ipinfo.cgi in IPCop (aka IPCop Firewall) before 2.1.3 allows remote attackers to inject arbitrary web script or HTML via the QUE | Jan 2, 2015 | 4.3 | 17 | NO | NO |
IPCop (aka IPCop Firewall) before 1.4.10 has world-readable permissions for the backup.key file, which might allow local users to overwrite system configuration files and gain priv | Dec 31, 2005 | 2.1 | 11 | NO | NO |
Race condition in IPCop (aka IPCop Firewall) before 1.4.10 might allow local users to overwrite system configuration files and gain privileges by replacing a backup archive during | Dec 31, 2005 | 1.2 | 10 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Ipcop.
Media articles that mention a CVE ID that affects a product developed by Ipcop — matched by CVE ID, not by vendor name.