dbcve.org
AleosOperating system · Sierrawireless

CVE-2019-11852

CRITICAL · 9.1 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 out-of-bounds reads vulnerability exists in the ACEView Service of ALEOS before 4.13.0, 4.9.5, and 4.4.9. Sensitive information may be disclosed via the ACEviewservice, accessible by default on the LAN.

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 confidence

An out-of-bounds read vulnerability in the ACEView Service of ALEOS firmware allows unauthenticated attackers on the LAN to read sensitive information from device memory due to improper bounds checking when processing requests.

MitigationUpgrade ALEOS firmware to version 4.13.0, 4.9.5, or 4.4.9 or later; additionally, network segment or firewall the ACEView service to limit exposure to trusted LAN clients only.

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.13.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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 ALEOS firmware version
    Access the device's web interface, CLI (via serial or SSH), or query via SNMP. Common CLI commands include 'ati', 'ati2', or 'show system info'. The firmware version is typically displayed in the system information or status page.
    Affected if The installed version is earlier than 4.13.0, 4.9.5, or 4.4.9 (depending on your release branch)
  2. Confirm ACEView service is enabled
    Log into the ALEOS web interface and navigate to Services or Applications settings. Look for ACEView or a related configuration section. Alternatively, check via CLI using 'aceview' or 'show config aceview' if available.
    Affected if ACEView is enabled and running on the device
  3. Verify ACEView network accessibility
    From a client on the same LAN segment, attempt to reach the ACEView service port (commonly HTTP/HTTPS on the device IP). Use 'curl http://<device_ip>/aceview' or check if the service responds to requests. Confirm the service listens on LAN-facing interfaces.
    Affected if The ACEView service is reachable from LAN clients without authentication
  4. Check for sensitive information exposure
    Send a crafted request to the ACEView endpoint and observe if arbitrary memory contents are returned in the response. A simple test: curl or access the ACEView URL and inspect the response for unexpected binary data or contents that do not match expected service behavior.
    Affected if The device returns data beyond expected boundaries or reveals memory contents

Your device is affected if it runs ALEOS firmware versions earlier than 4.13.0, 4.9.5, or 4.4.9, has ACEView enabled, and the service is accessible from LAN clients.

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.13.0 or later
Fixed in 4.4.94.9.54.13.0
Interim mitigation

Upgrade ALEOS firmware to version 4.13.0, 4.9.5, or 4.4.9 or later; additionally, network segment or firewall the ACEView service to limit exposure to trusted LAN clients only.

Recommended fix High confidence

Aleos 4.13.0 (or 4.9.5/4.4.9 depending on your branch)

  1. 1. Identify the current Aleos firmware version running on the Sierra Wireless device
  2. 2. Determine which version branch (4.4.x, 4.9.x, or 4.13.x) the device is running
  3. 3. Download the appropriate fixed Aleos firmware version from Sierra Wireless (4.4.9 or later, 4.9.5 or later, or 4.13.0 or later)
  4. 4. Review release notes for any configuration or behavioral changes before upgrading
  5. 5. Back up the current device configuration
  6. 6. Upload and install the new Aleos firmware via the device's web interface or CLI
  7. 7. After upgrade, verify the ACEView Service is functioning correctly
  8. 8. Confirm the new version is running and the vulnerability is resolved
Caveat Review Sierra Wireless release notes for your specific version branch; major version upgrades may introduce configuration or feature changes

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

Fix this in Aleos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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