Crash via unchecked BT ATT opcode
Published Jan 16, 2020 · Updated Aug 4, 2024
NULL pointer dereference in the BT ATT dissector in Wireshark 3.0.0 through 3.0.7 allows attackers to crash Wireshark via malformed packets. In dissect_btatt, opcode-specific data is dereferenced without first validating that the opcode has an associated entry, producing a NULL-pointer read. The crash requires a malformed packet on a monitored link or a crafted packet trace to be opened, and the demonstrated consequence is process termination only.
Summary
What happened
NULL pointer dereference in the BT ATT dissector in Wireshark 3.0.0 through 3.0.7 allows attackers to crash Wireshark via malformed packets. In dissect_btatt, opcode-specific data is dereferenced without first validating that the opcode has an associated entry, producing a NULL-pointer read. The crash requires a malformed packet on a monitored link or a crafted packet trace to be opened, and the demonstrated consequence is process termination only.
The record
- CVE
- CVE-2020-7045
- Published
- Jan 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Malformed BT ATT packet fuzz reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo