CVE-2019-5598 json
In FreeBSD 11.3-PRERELEASE before r345378, 12.0-STABLE before r345377, 11.2-RELEASE before 11.2-RELEASE-p10, and 12.0-RELEASE before 12.0-R…
published 7y ago modified 4mo ago also EUVD-2019-15173
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
In FreeBSD 11.3-PRERELEASE before r345378, 12.0-STABLE before r345377, 11.2-RELEASE before 11.2-RELEASE-p10, and 12.0-RELEASE before 12.0-RELEASE-p4, a bug in pf does not check if the outer ICMP or ICMP6 packet has the same destination IP as the source IP of the inner protocol packet allowing a maliciously crafted ICMP/ICMP6 packet could bypass the packet filter rules and be passed to a host that would otherwise be unavailable.
Patch / fix
Is CVE-2019-5598 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.34% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- n/a FreeBSD
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
security.freebsd.org
/advisories/FreeBSD-SA-19:06.pf.asc
patch, vendor-advisory
-
synacktiv.com
/posts/systems/icmp-reachable.html
third-party-advisory
-
packetstormsecurity.com
/files/152934/FreeBSD-Security-Advisory-FreeBSD-SA-19-06.pf.html
third-party-advisory, vdb-entry
-
securityfocus.com
/bid/108395
vdb-entry
- security.netapp.com /advisory/ntap-20190611-0001/
- oracle.com /technetwork/security-advisory/cpujul2019-5072835.html
- seclists.org /fulldisclosure/2025/Apr/1
Sources
- CVE List CVE-2019-5598
- NVD CVE-2019-5598
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.