basicsecurity.net
Proof, not just disclosure.
Threats / Cisco / CVE-2004-1464
CVE-2004-1464 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Cisco IOS vulnerability

Cisco IOS contains an unspecified vulnerability that blocks telnet, reverse telnet, RSH, SSH, and HTTP access to affected devices, causing denial of service.

Verdict

Today item — known-exploited.

An attacker can trigger a denial-of-service condition by exploiting an unspecified flaw in Cisco IOS, rendering remote management interfaces inaccessible and preventing legitimate administrative access to network devices.

CISA KEV Yes · 2023-05-193EPSS 0.05133 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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 2023-05-19).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.05133 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Cisco, IOS. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious input or trigger a specific condition in Cisco IOS to activate the vulnerability.
Business
Network administrators lose remote access to critical infrastructure devices, disrupting operational visibility and control.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I block all remote management protocols including SSH, telnet, and HTTP on the target device.
Business
Incident response and remediation efforts are delayed, extending downtime and increasing business impact.
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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 2 reported-exploitation source(s)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.