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

Cisco IOS XR vulnerability

Cisco IOS XR with BGP routing enabled is vulnerable to remote denial-of-service attacks via improper input validation.

Verdict

Today item — known-exploited.

A remote attacker can trigger a denial-of-service condition in Cisco IOS XR systems running BGP by sending specially crafted network traffic. The vulnerability stems from insufficient input validation and has been observed in active exploitation.

CISA KEV Yes · 2022-03-253EPSS 0.05562 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.05562 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Cisco, IOS XR. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 malformed BGP packets and send them to the target IOS XR device to trigger a crash or service hang.
Business
Network routing infrastructure becomes unavailable, disrupting all traffic dependent on that device until manual recovery.
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)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by cisco (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 ciscoCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.