Threats / Looking Glass / CVE-2014-3931
CVE-2014-3931
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Looking Glass Multi-Router (MRLG) vulnerability
Multi-Router Looking Glass (MRLG) contains a buffer overflow vulnerability allowing remote attackers to write to arbitrary memory locations and corrupt memory.
Verdict
Today item — known-exploited.
A buffer overflow in MRLG enables remote code execution and system compromise without authentication. The vulnerability has been exploited in the wild and poses significant risk to exposed router management interfaces.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-07-07).
Probability (EPSS)
EPSS 0.26572 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Looking Glass, Multi-Router Looking Glass (MRLG). Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious input exceeding buffer boundaries in MRLG to overwrite adjacent memory regions.
Business
Attackers gain ability to execute arbitrary code on critical network infrastructure with potential for widespread routing disruption.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage memory corruption to hijack control flow and execute my payload on the affected router.
Business
Network availability and integrity are compromised, enabling traffic interception, redirection, or denial of service across dependent systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access to the router management layer for lateral movement within the network.
Business
Organizational network perimeter is breached, creating pathways for further compromise of internal systems and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05