CVE-2014-3931
fastping.c in MRLG (aka Multi-Router Looking Glass) before 5.5.0 allows remote attackers to cause an arbitrary memory write and memory corruption.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. This is a memory-corruption bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2014-3931 being exploited?
Yes. CVE-2014-3931 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2014-3931?
CVE-2014-3931 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2014-3931?
Not known from our data. No patch reference has been recorded for CVE-2014-3931, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2014-3931 affect?
CVE-2014-3931 affects multi-router_looking_glass_project:multi-router_looking_glass. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 17 Jul 2025 (SSVC 2.0.3).
timeline
- 31 Mar 2017Published
- 7 Jul 2025Added to CISA KEV (exploited in the wild) · 3,019 days (about 8 years) later
- 17 Jul 2025CISA SSVC assessment: exploitation active · 10 days later
- 28 Jul 2025CISA remediation due date (US federal agencies) · 11 days later
- 21 Oct 2025CVE record last updated · 86 days (about 3 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkmrlg.op-sec.us /
- Links3.eurecom.fr /cve/CVE-2014-3931.txt
- Linkhackerone.com /reports/16330
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-3931
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.