Threats / Zyxel / CVE-2024-11667
CVE-2024-11667
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Zyxel Multiple Firewalls vulnerability
Multiple Zyxel firewalls contain a path traversal vulnerability in the web management interface allowing attackers to download or upload files via crafted URLs.
Verdict
Today item, not a backlog item.
Path traversal in Zyxel firewall web interfaces enables unauthorized file access and modification. Active exploitation and ransomware deployment observed. Immediate patching required for affected firewall models.
CISA KEV Yes · 2024-12-035Ransomware use Flagged5EPSS 0.02929 (verify live)6CVSS 7.53CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 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 2024-12-03), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.02929 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) · Affected: Zyxel, Multiple Firewalls. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 6 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
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 URL with path traversal sequences to bypass directory restrictions on the Zyxel firewall web interface.
Business
Attackers gain unauthorized access to sensitive firewall configuration files and system data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I upload malicious files to arbitrary locations on the firewall system by exploiting the path traversal flaw.
Business
Compromised firewall becomes a pivot point for lateral movement into the protected network infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I download critical firewall configurations and credentials stored on the device.
Business
Extracted credentials and network topology enable broader organizational compromise.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware payloads through the compromised firewall to encrypt systems across the network.
Business
Organization faces operational shutdown, data loss, and extortion demands from ransomware operators.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by ZyxelCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.