CVE-2014-4168: (1) iodined.c and (2) user.c in iodine before 0.7.0 allows remote attackers to bypass authentication by contin
CVE-2014-4168 is a medium-severity flaw (CVSS 5.0) affecting iodine. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
(1) iodined.c and (2) user.c in iodine before 0.7.0 allows remote attackers to bypass authentication by continuing execution after an error has been triggering.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.0 (Medium) |
| EPSS exploit chance | 3.8% (top 10%) |
| CISA exploited list | No |
| Weakness | CWE-287 |
| Published | 2014-07-03 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2014-4168?
iodine: upgrade to newer than 0.6.0. Exact commands for each OS are on this page.
Is CVE-2014-4168 being exploited?
CVE-2014-4168 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2014-4168 affect?
CVE-2014-4168 affects iodine. Severity is medium (CVSS 5.0). (1) iodined.c and (2) user.c in iodine before 0.7.0 allows remote attackers to bypass authentication by continuing execution after an error has been triggering.
How urgent is CVE-2014-4168?
Priority 40/100. No elevated risk signals yet.
Related CVEs
- CVE-2024-22050 HIGH 7.5 UPGRADE Path traversal in the static file service in Iodine less than 0.7.33 allows an unauthenticated, remote attacke