Asr 5000 Series SoftwareApplication · Cisco
CVE-2017-6612
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 · uneditedA vulnerability in the gateway GPRS support node (GGSN) of Cisco ASR 5000 Series Aggregation Services Routers 17.3.9.62033 through 21.1.2 could allow an unauthenticated, remote attacker to redirect HTTP traffic sent to an affected device. More Information: CSCvc67927.
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 confidenceThis is a vulnerability in the Gateway GPRS Support Node (GGSN) component of Cisco ASR 5000 Series routers. An unauthenticated, remote attacker can exploit this to redirect HTTP traffic destined for the affected device, potentially enabling traffic interception or redirection attacks.
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 5000 Series SoftwareApplication
= 17.3.9.62033= 17.7.5= 19.6.3= 20.1.2= 20.2.12= 21.0.1= 21.1.2CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelExecute 'show hardware' or check the physical device label to confirm the model is Cisco ASR 5000 SeriesAffected if Device is not a Cisco ASR 5000 Series router (vulnerability only affects this platform)
-
Determine the installed software versionExecute 'show version' or 'show software' command on the device CLI to retrieve the active software versionAffected if Installed version matches any of these: 17.3.9.62033, 17.7.5, 19.6.3, 20.1.2, 20.2.12, 21.0.1, or 21.1.2
-
Verify GGSN service is configuredExecute 'show ggsn service' or 'show configuration ggsn' to check if Gateway GPRS Support Node service is enabled on the deviceAffected if GGSN service is active and the software version matches an affected version from step 2
-
Inspect for HTTP redirect configurationsReview GGSN configuration with 'show configuration ggsn' or check active HTTP redirect rules that may indicate unauthorized traffic redirectionAffected if Unexpected HTTP redirect rules exist that were not intentionally configured
A user is affected if they run Cisco ASR 5000 Series software version 17.3.9.62033, 17.7.5, 19.6.3, 20.1.2, 20.2.12, 21.0.1, or 21.1.2 with GGSN service enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco ASR 5000 Series routers to a version beyond 21.1.2, and implement network segmentation and traffic monitoring to detect unauthorized HTTP redirect attempts.
Fix this in Asr 5000 Series Software
Scoped from the published advisory
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6612 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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