dbcve.org
Ios XeOperating system · Cisco

CVE-2014-3284

MEDIUM · 6.1 CVSS v2.0 Published 2014-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cisco IOS XE on ASR1000 devices, when PPPoE termination is enabled, allows remote attackers to cause a denial of service (device reload) via a malformed PPPoE packet, aka Bug ID CSCuo55180.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This CVE affects Cisco IOS XE on ASR1000 series routers when PPPoE (Point-to-Point Protocol over Ethernet) termination is enabled. A remote attacker can send a malformed PPPoE packet to trigger a denial of service, causing the device to reload unexpectedly. The vulnerability has a CVSS score of 6.1 (Medium), reflecting network accessibility but limited confidentiality or integrity impact.

MitigationApply the relevant Cisco IOS XE software update/patch for this bug (CSCuo55180). As a temporary workaround, disable PPPoE termination if not required, or implement filtering for PPPoE traffic at network edge.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ios XeOperating system
Affected:all versions
Asr 1001Hardware / appliance
Affected:all versions
Asr 1002Hardware / appliance
Affected:all versions
Asr 1002 XHardware / appliance
Affected:all versions
Asr 1002 Fixed RouterHardware / appliance
Affected:all versions
Asr 1004Hardware / appliance
Affected:all versions
Asr 1006Hardware / appliance
Affected:all versions
Asr 1013Hardware / appliance
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:A/AC:L/Au:N/C:N/I:N/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Run 'show version' or 'show inventory' to confirm the hardware is an ASR1000 series router (ASR1001, ASR1002, ASR1002X, ASR1004, ASR1006, or ASR1013)
    Affected if The device is not an ASR1000 series router - not affected
  2. Confirm IOS XE is running
    Run 'show version' and look for 'IOS XE' in the software version string
    Affected if The device does not run IOS XE - not affected
  3. Check if PPPoE termination is enabled
    Run 'show running-config | include pppoe' or 'show ip interface' to look for PPPoE-related interfaces. Also check interface configurations with 'show running-config interface' for any 'pppoe enable' or 'pppoe termination' statements
    Affected if PPPoE termination is not configured on any interface - not affected (the vulnerability requires PPPoE to be enabled)

The device is affected if it is an ASR1000 series router running IOS XE with PPPoE termination enabled on any interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco IOS XE software update/patch for this bug (CSCuo55180). As a temporary workaround, disable PPPoE termination if not required, or implement filtering for PPPoE traffic at network edge.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3284 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data