CVE-2019-11478
No exploitation reported yet. Patch in your normal cycle; we flag it the day exploitation starts.
What it is
Jonathan Looney discovered that the TCP retransmission queue implementation in tcp_fragment in the Linux kernel could be fragmented when handling certain TCP Selective Acknowledgment (SACK) sequences. A remote attacker could use this to cause a denial of service. This has been fixed in stable kernel releases 4.4.182, 4.9.182, 4.14.127, 4.19.52, 5.1.11, and is fixed in commit f070ef2ac66716357066b683fb0baf55f8191a2e.
Live exploitation on the huntback network (30 days)
Detection
Evidence
No exploitation known. EPSS puts the chance of exploitation in the next 30 days at 94%.
Published
Observed: our own decoys saw it. Reported: CISA, the vendor or another named source says so. Weaponised: public exploit code or a scanner template exists. Methodology
Questions
Is CVE-2019-11478 being exploited in the wild?
Not on our sensors so far: the huntback decoy network has not captured an exploitation attempt, and it is not in the CISA KEV catalogue.
Can CVE-2019-11478 be detected on the network?
huntback has no wire signature for CVE-2019-11478 yet; it may need local or authenticated access to exploit.
How huntback helps
Deploy a decoy that emulates Big-ip Access Policy Manager and you will see every attempt at this CVE the moment it lands, with the full payload, the attacker's infrastructure, and any stage-2 loader. Then huntback can scan the attacker back.
Related
NVD record → Browse all CVEs → Live malware and C2 finds → Novel-attack discovery → Deploy a decoy →API
This record, with its evidence timeline, as JSON:
curl -H "X-API-Key: $HUNTBACK_KEY" https://app.huntback.io/api/v1/evidence/CVE-2019-11478