Vulnerabilities with 3.0
Hello, What are the associated vulnerabilities with Wireshark version 3.0.0.
Thank you!
-Me
2 Answers
- Sort by
oldest newest most voted
0
You could lookup the CVE numbers assigned to Wireshark and check which versions they apply to:
https://www.cvedetails.com/product/82...
If you're worried about attacks against Wireshark you might also want to read this:
0
Note sure if it fits this description but here we go:
More of an error to me with Health level 7 protocol, and it turns out that Health level 7 protocol is kinda error prone because if you turn on the checkbox "Display raw text for HL7 message", Wireshark v3.0.0 will throw an error saying in a CMD debugger "Err Preference tcp.port has already been registered". I dont know if other verisons do this as well either but its been an ongoing issue ive found.
Now, I found a fix to that thankfully. Going to the preferences file in appdata WITHOUT having wireshark launched, and goto (or find) the text where it says this: "# Specifies that the raw text of the HL7 message should be displayed in addition to the dissection tree TRUE or FALSE (case-insensitive) hl7.display_raw: TRUE" << please change that to FALSE in order to get rid of the error and debugger. << That will need fixing in the future.
Comments
This should really be another question, even then it's probably better to go straight to the Wireshark bugzilla and raise a bug report.
And, in fact, if you find any ongoing issues, please report them as bugs; the Q&A site may be a place to ask whether some behavior is a bug, but if it's obvious that it's a bug, the right place to report it is the bug database.
Your Answer
Please start posting anonymously - your entry will be published after you log in or create a new account.
This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.
Comments