dbcve.org
Asr 5500 FirmwareOperating system · Cisco

CVE-2017-12217

MEDIUM · 5.3 CVSS v3.0 Published 2017-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability in the General Packet Radio Service (GPRS) Tunneling Protocol ingress packet handler of Cisco ASR 5500 System Architecture Evolution (SAE) Gateways could allow an unauthenticated, remote attacker to cause a partial denial of service (DoS) condition on an affected device. The vulnerability is due to improper input validation of GPRS Tunneling Protocol packet headers. An attacker could exploit this vulnerability by sending a malformed GPRS Tunneling Protocol packet to an affected device. A successful exploit could allow the attacker to cause the GTPUMGR process on an affected device to restart unexpectedly, resulting in a partial DoS condition. If the GTPUMGR process restarts, there could be a brief impact on traffic passing through the device. Cisco Bug IDs: CSCve07119.

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

A vulnerability in the GPRS Tunneling Protocol (GTP) ingress packet handler of Cisco ASR 5500 SAE Gateways allows unauthenticated remote attackers to send malformed GTP packets with improper headers. Successful exploitation causes the GTPUMGR process to restart unexpectedly, resulting in a partial denial of service condition and brief traffic disruption.

MitigationApply the Cisco patch for bug CSCve07119 (firmware update). Additionally, implement ingress filtering at network boundaries to block malformed or malformed GTP packets from untrusted sources.

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
Asr 5500 FirmwareOperating system
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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Confirm device model is Cisco ASR 5500
    Identify the installed hardware by checking the system inventory or device model number through CLI command 'show hardware' or equivalent system information display
    Affected if The device is a Cisco ASR 5500 SAE Gateway
  2. Verify GTP feature is enabled
    Check if the GPRS Tunneling Protocol feature is active on the device by examining the running configuration or using 'show gtp' CLI command if available
    Affected if GTP feature is configured and active on the device
  3. Check for GTPUMGR process status
    Use process monitoring commands such as 'show process' or 'show process name gtpumgr' to verify the GTPUMGR process is running
    Affected if The GTPUMGR process is present and running on the device
  4. Review logs for GTPUMGR restarts
    Examine system logs, crash logs, or use 'show logging' command to look for unexpected GTPUMGR process restarts or failures
    Affected if GTPUMGR process has restarted unexpectedly or shows crash/restart events in the logs
  5. Inspect GTP packet handling
    Monitor GTP ingress traffic statistics using 'show gtp statistics' or similar command to identify malformed packet errors or anomalies
    Affected if Malformed GTP packets are being processed or logged by the system

If the device is a Cisco ASR 5500 with GTP enabled and the GTPUMGR process is exhibiting unexpected restarts without clear explanation, the environment is likely affected by this vulnerability.

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 Cisco patch for bug CSCve07119 (firmware update). Additionally, implement ingress filtering at network boundaries to block malformed or malformed GTP packets from untrusted sources.

Fix this in Asr 5500 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12217 — 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-2017-12217 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