CVE-2019-10900
First published: Tue Apr 09 2019(Updated: )
In Wireshark 3.0.0, the Rbm dissector could go into an infinite loop. This was addressed in epan/dissectors/file-rbm.c by handling unknown object types safely.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Wireshark Wireshark | =3.0.0 | |
| Fedora | =29 | |
| Fedora | =30 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00027.html
- http://www.securityfocus.com/bid/107836
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15612
- https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=26eee01f57f0a86fb375892c7937eac24ede4610
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4LYIOOQIMFQ3PA7AFBK4DNXHISTEYUC5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PU3QA2DUO3XS24QE24CQRP4A4XQQY76R/
- https://www.wireshark.org/security/wnpa-sec-2019-13.html
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=26eee01f57f0a86fb375892c7937eac24ede4610
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PU3QA2DUO3XS24QE24CQRP4A4XQQY76R/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4LYIOOQIMFQ3PA7AFBK4DNXHISTEYUC5/
Frequently Asked Questions
What is the severity of CVE-2019-10900?
CVE-2019-10900 has a medium severity level due to its potential to cause denial of service through an infinite loop.
How do I fix CVE-2019-10900?
To fix CVE-2019-10900, update Wireshark to version 3.0.1 or later, where the issue has been resolved.
What software is affected by CVE-2019-10900?
CVE-2019-10900 affects Wireshark version 3.0.0 and certain versions of Fedora (29 and 30) when using that specific Wireshark version.
What impact does CVE-2019-10900 have on Wireshark?
CVE-2019-10900 could cause Wireshark to become unresponsive due to an infinite loop when processing certain packet types.
Who is responsible for the fix of CVE-2019-10900?
The maintainers of Wireshark are responsible for addressing CVE-2019-10900 by implementing safe handling of unknown object types in the Rbm dissector.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/severity
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/wireshark
- canonical/wireshark wireshark
- version/wireshark wireshark/3.0.0
- vendor/fedoraproject
- canonical/fedoraproject fedora
- version/fedoraproject fedora/29
- version/fedoraproject fedora/30