CVE-2020-11101
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 · uneditedSierra Wireless AirLink Mobility Manager (AMM) before 2.17 mishandles sessions and thus an unauthenticated attacker can obtain a login session with administrator privileges.
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 AirLink Mobility Manager before version 2.17 contains a session management flaw that allows an unauthenticated remote attacker to obtain a valid administrator login session. This session hijacking vulnerability is exploitable without credentials and grants full administrative access to the device management interface.
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< 2.17CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 AirLink Mobility Manager versionAccess the AMM management interface and navigate to System > Status or About page to view the firmware/software version. Alternatively, check the login page footer or banner for version information.Affected if The displayed version number is less than 2.17 (e.g., 2.16, 2.15, etc.)
-
Verify management interface network exposureCheck firewall rules or network ACLs to determine if the AMM web management interface (typically ports 443 or 8443) is accessible from untrusted or external networks.Affected if The management interface is exposed to the internet or untrusted networks without IP restrictions
-
Inspect active administrative sessionsLog into the AMM admin panel and review the session management or active users section to see if there are any unexpected or unauthorized admin sessions active.Affected if Unexpected admin sessions exist from IP addresses you do not recognize
-
Review authentication logsExamine AMM system logs or authentication logs for any successful admin logins that you cannot account for, especially from external IP addresses.Affected if There are admin-level login events that were not performed by your authorized administrators
You are affected if your AirLink Mobility Manager version is below 2.17 and the management interface is network-accessible to potential attackers.
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.
dbcve · scoped2.17
Upgrade Sierra Wireless AirLink Mobility Manager to version 2.17 or later to remediate the session mishandling vulnerability. If immediate upgrade is not possible, restrict network access to the AMM management interface to trusted sources.
Airlink Mobility Manager 2.17
- 1. Identify all deployed instances of Sierra Wireless AirLink Mobility Manager (AMM) in the environment
- 2. Check the current version of each AMM installation
- 3. If version is below 2.17, plan for upgrade to version 2.17 or later
- 4. Before upgrading, backup current configuration and data
- 5. Follow Sierra Wireless official upgrade procedures for AMM
- 6. After upgrade, verify the new version is 2.17 or higher
- 7. Test that authentication and session handling work correctly
- 8. Monitor for any unusual admin session activity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11101 — 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-2020-11101 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