cve/2019/CVE-2019-10900.md

### [CVE-2019-10900](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10900)
![](https://img.shields.io/static/v1?label=Product&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

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.

### POC

#### Reference
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15612
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15612

#### Github
No PoCs found on GitHub currently.
Update Sun May 26 14:27:04 CEST 2024 2024-05-26 14:27:05 +02:00			`### [CVE-2019-10900](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10900)`
			`![](https://img.shields.io/static/v1?label=Product&message=n%2Fa&color=blue)`
			`![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)`
			`![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)`

			`### Description`

			`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.`

			`### POC`

			`#### Reference`
			`- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15612`
Update CVE sources 2024-06-09 00:33 2024-06-09 00:33:16 +00:00			`- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15612`
Update Sun May 26 14:27:04 CEST 2024 2024-05-26 14:27:05 +02:00
			`#### Github`
			`No PoCs found on GitHub currently.`