CVE-2017-15190
UnknownEPSS 1.69%
Last modified
CVE-2017-15190 is a vulnerability of currently unknown severity. In Wireshark 2.4.0 to 2.4.1, the RTSP dissector could crash. This was addressed in epan/dissectors/packet-rtsp.c by correcting the scope of a variable.. EPSS estimates a 1.69% chance of exploitation in the next 30 days.
Description
In Wireshark 2.4.0 to 2.4.1, the RTSP dissector could crash. This was addressed in epan/dissectors/packet-rtsp.c by correcting the scope of a variable.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | 2.4.0 |
| Wireshark | Wireshark | 2.4.1 |
References
- http://www.securityfocus.com/bid/101229Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14077Issue Tracking, Vendor Advisory
- https://code.wireshark.org/review/23635Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-45.htmlVendor Advisory
- http://www.securityfocus.com/bid/101229Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14077Issue Tracking, Vendor Advisory
- https://code.wireshark.org/review/23635Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-45.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-15190?
In Wireshark 2.4.0 to 2.4.1, the RTSP dissector could crash. This was addressed in epan/dissectors/packet-rtsp.c by correcting the scope of a variable.
How severe is CVE-2017-15190?
Severity scoring for CVE-2017-15190 is pending analysis. The EPSS model estimates a 1.69% probability of exploitation in the next 30 days.
How do I fix CVE-2017-15190?
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-15190?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST