CVE-2019-11850
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 stack overflow vulnerabiltity exist in the AT command interface of ALEOS before 4.11.0. The vulnerability may allow code execution
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 confidenceStack overflow vulnerability in the AT command interface of ALEOS firmware before version 4.11.0, potentially allowing arbitrary code execution via specially crafted AT commands.
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< 4.11.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 Sierra Wireless ALEOS deviceConfirm the device is a Sierra Wireless gateway/router running ALEOS firmware. Check device model number and documentation or access the device web interface/admin panel to verify the product name.Affected if Device is not a Sierra Wireless ALEOS product
-
Locate firmware version informationAccess the device admin interface (web UI or serial console) and navigate to System Status, About, or Firmware Information page. Alternatively, use AT command 'AT+CGMR' or 'AT!ENTERCND="xxx"' followed by 'AT!GENIO?' to retrieve firmware version.Affected if Unable to retrieve firmware version information
-
Compare installed version to affected rangeNote the displayed firmware version number (format typically like 4.x.x) and compare against 4.11.0. Check if version is below 4.11.0 (for example, 4.9.3, 4.10.0, etc.).Affected if Installed firmware version is less than 4.11.0
-
Verify AT command interface is enabledConfirm the AT command interface is accessible on the device (typically via serial port, telnet, or HTTP API). Check device configuration for AT command enable settings or test with a basic AT command.Affected if AT command interface is enabled and accessible on the device
Device is affected if it runs Sierra Wireless ALEOS firmware version below 4.11.0 and has the AT command interface 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 data4.11.0
Upgrade ALEOS firmware to version 4.11.0 or later to remediate the stack overflow vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11850 — 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-2019-11850 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