CVE-2020-11984
No exploitation reported yet. Patch in your normal cycle; we flag it the day exploitation starts.
What it is
Apache HTTP server 2.4.32 to 2.4.44 mod_proxy_uwsgi info disclosure and possible RCE
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 90%.
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-2020-11984 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-2020-11984 be detected on the network?
huntback has no wire signature for CVE-2020-11984 yet; it may need local or authenticated access to exploit.
How huntback helps
Deploy a decoy that emulates Clustered Data Ontap 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-2020-11984