dbcve.org
AleosOperating system · Sierrawireless

CVE-2019-11855

CRITICAL · 9.8 CVSS v3.1 Published 2020-08-21
Fix available
A fix is available. Upgrade to 4.4.9 / 4.9.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An RPC server is enabled by default on the gateway's LAN of ALEOS before 4.12.0, 4.9.5, and 4.4.9.

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

An RPC server is enabled by default on the LAN interface of ALEOS-based Sierra Wireless gateways in versions prior to 4.12.0, 4.9.5, and 4.4.9. This exposes an unauthenticated administrative interface on the local network, potentially allowing remote code execution or full device compromise without any authentication from the LAN segment.

MitigationUpgrade ALEOS firmware to version 4.12.0, 4.9.5, 4.4.9 or later. If immediate patching is not feasible, disable or restrict access to the LAN-facing RPC service through firewall rules or network segmentation.

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
AleosOperating system
Affected:< 4.12.0< 4.9.5< 4.4.9

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device and confirm ALEOS firmware
    Access the device management interface or check the device label/model to confirm it is a Sierra Wireless gateway running ALEOS firmware.
    Affected if The device is not an ALEOS-based Sierra Wireless gateway.
  2. Check the installed ALEOS version
    Access the device web interface or CLI and locate the firmware version information, typically found in the system status or firmware upgrade section.
    Affected if The installed version is prior to 4.12.0, 4.9.5, or 4.4.9 (for example, 4.11.x, 4.8.x, or 4.3.x).
  3. Verify if RPC service is exposed on LAN interface
    From a host on the same LAN segment as the gateway, attempt to access the RPC service port (commonly port 8083 or similar) on the gateway's LAN IP address using a web browser or network scanner.
    Affected if The RPC service responds and presents an administrative interface without requiring login credentials.
  4. Test administrative access without authentication
    Attempt to access common administrative URLs or endpoints on the gateway's LAN IP address without providing any username or password.
    Affected if Administrative functions or device configuration pages are accessible without authentication.

The environment is affected if the device is a Sierra Wireless ALEOS gateway running firmware version prior to 4.12.0, 4.9.5, or 4.4.9 AND the RPC administrative interface is accessible from the LAN without authentication.

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.

dbcve · scoped
Upgrade available Upgrade to 4.4.9 / 4.9.5 / 4.12.0 or later
Fixed in 4.4.94.9.54.12.0
Interim mitigation

Upgrade ALEOS firmware to version 4.12.0, 4.9.5, 4.4.9 or later. If immediate patching is not feasible, disable or restrict access to the LAN-facing RPC service through firewall rules or network segmentation.

Recommended fix High confidence

Aleos 4.12.0 (or latest stable 4.x release in your respective branch)

  1. 1. Identify the current ALEOS version running on the Sierra Wireless gateway
  2. 2. For users on ALEOS 4.4.x branch: upgrade to version 4.4.9 or later
  3. 3. For users on ALEOS 4.9.x branch: upgrade to version 4.9.5 or later
  4. 4. For users on ALEOS 4.10.x or 4.11.x branch: upgrade to version 4.12.0 or later
  5. 5. After upgrading, verify the RPC server configuration via the gateway's web interface or CLI to ensure it meets security requirements
  6. 6. If staying on an older branch (4.4.x or 4.9.x), consider upgrading to the latest stable 4.12.x release for additional security fixes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aleos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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