CVE-2014-3857 json
Multiple SQL injection vulnerabilities in Kerio Control Statistics in Kerio Control (formerly WinRoute Firewall) before 8.3.2 allow remote…
published 12y ago modified 4mo ago also EUVD-2014-3794
- cvss
- 6.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Kerio Control Statistics in Kerio Control (formerly WinRoute Firewall) before 8.3.2 allow remote authenticated users to execute arbitrary SQL commands via the (1) x_16 or (2) x_17 parameter to print.php.
Is CVE-2014-3857 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-33954)
- Published
Exploit prediction
2.17% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-33954 Kerio Control 8.3.1 - Blind SQL Injection webapps, 2014-07-02
- fereidani.com http://fereidani.com/articles/show/76_kerio_control_8_3_1_boolean_based_blind_sql_injection referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/33954
exploit
-
fereidani.com
/articles/show/76_kerio_control_8_3_1_boolean_based_blind_sql_injection
exploit
-
secunia.com
/advisories/59215
third-party-advisory
- kerio.com /support/kerio-control/release-history
- packetstormsecurity.com /files/127320/Kerio-Control-8.3.1-Blind-SQL-Injection.html
-
securityfocus.com
/archive/1/532607/100/0/threaded
mailing-list
-
osvdb.org
/show/osvdb/108584
vdb-entry
Sources
- CVE List CVE-2014-3857
- NVD CVE-2014-3857
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.