StarosOperating system · Cisco
CVE-2015-0711
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 · uneditedThe hamgr service in the IPv6 Proxy Mobile (PM) implementation in Cisco StarOS 18.1.0.59776 on ASR 5000 devices allows remote attackers to cause a denial of service (service reload and call-processing outage) via malformed PM packets, aka Bug ID CSCut94711.
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 · moderate confidenceThe hamgr service in the IPv6 Proxy Mobile (PM) implementation in Cisco StarOS 18.1.0.59776 on ASR 5000 devices contains a vulnerability where malformed PM packets can trigger a denial of service, causing service reload and call-processing outage.
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
StarosOperating system
= 18.1.0.59776CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 modelVerify the hardware is a Cisco ASR 5000 series device. Use 'show hardware' or check the chassis inventory.Affected if The device is not an ASR 5000 series device - this vulnerability only affects ASR 5000 platforms.
-
Check the StarOS versionExecute 'show version' or 'show software version' to confirm the running StarOS version.Affected if The version is exactly 18.1.0.59776 - this is the only version listed as affected by this CVE.
-
Verify IPv6 Proxy Mobile is configuredCheck if IPv6 PM is enabled on the system using 'show config' or 'show ip6 proxy-mobile configuration'. Look for proxy-mobile IPv6 policies or contexts.Affected if IPv6 Proxy Mobile feature is enabled - the vulnerability exists in the hamgr service handling PM packets, so the feature must be active.
-
Inspect hamgr service statusUse 'show hamgr' or 'show process hamgr' to check the hamgr service status and whether it is handling PM operations.Affected if The hamgr service is running and actively handling Proxy Mobile sessions - this is the specific service component that contains the flaw.
A user is affected if they are running StarOS version 18.1.0.59776 on an ASR 5000 device with IPv6 Proxy Mobile feature enabled and the hamgr service active, where malformed PM packets could trigger a denial of service.
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 dataApply the Cisco fix for Bug ID CSCut94711 (StarOS update). If unavailable, implement network-level filtering of malformed PM packets or consider isolating affected ASR 5000 devices until the patch can be applied.
Fix this in Staros
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0711 — 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-2015-0711 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