CVE-2017-5205
UnknownEPSS 3.50%
Last modified
CVE-2017-5205 is a vulnerability of currently unknown severity. The ISAKMP parser in tcpdump before 4.9.0 has a buffer overflow in print-isakmp.c:ikev2_e_print().. EPSS estimates a 3.50% chance of exploitation in the next 30 days.
Description
The ISAKMP parser in tcpdump before 4.9.0 has a buffer overflow in print-isakmp.c:ikev2_e_print().
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Tcpdump | Tcpdump | < 4.9.0 |
| Debian | Debian Linux | 8.0 |
| Debian | Debian Linux | 9.0 |
| Redhat | Enterprise Linux Desktop | 7.0 |
| Redhat | Enterprise Linux Server | 7.0 |
| Redhat | Enterprise Linux Server Aus | 7.4 |
| Redhat | Enterprise Linux Server Aus | 7.6 |
| Redhat | Enterprise Linux Server Eus | 7.4 |
| Redhat | Enterprise Linux Server Eus | 7.5 |
| Redhat | Enterprise Linux Server Eus | 7.6 |
| Redhat | Enterprise Linux Server Tus | 7.6 |
| Redhat | Enterprise Linux Workstation | 7.0 |
References
- http://www.debian.org/security/2017/dsa-3775Third Party Advisory
- http://www.securityfocus.com/bid/95852Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037755Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:1871Third Party Advisory
- https://security.gentoo.org/glsa/201702-30Third Party Advisory
- http://www.debian.org/security/2017/dsa-3775Third Party Advisory
- http://www.securityfocus.com/bid/95852Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037755Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:1871Third Party Advisory
- https://security.gentoo.org/glsa/201702-30Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5205?
The ISAKMP parser in tcpdump before 4.9.0 has a buffer overflow in print-isakmp.c:ikev2_e_print().
How severe is CVE-2017-5205?
Severity scoring for CVE-2017-5205 is pending analysis. The EPSS model estimates a 3.50% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5205?
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-2017-5205?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
