CVE-2015-2897 is a set of hard-coded root accounts in Sierra Wireless ALEOS 4.4.1 and earlier on AirLink GX, ES and LS cellular gateways. A remote attacker who reaches SSH or Telnet on the gateway can log in with those accounts and take full control. NVD scores it CVSS v2 10.0, and ALEOS 4.4.2 disables access to the accounts by default.
Vulnerability summary
CVSS base score
10
Critical severity
EPSS score (FIRST)
2.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2015-2897 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Sierra Wireless AirLink GX440, GX450, ES440, ES450 and LS300 gateways (ALEOS) | cpe:2.3:a:sierrawireless:aleos:*:*:*:*:*:*:*:* | ALEOS 4.4.1 and earlier; fixed in ALEOS 4.4.2 (CERT/CC VU#628568). Remote access to the accounts is on by default up to 4.3.4 and off by default in 4.3.5 to 4.4.1 |
What does this mean for affected devices?
NVD describes the flaw as follows: "Sierra Wireless ALEOS before 4.4.2 on AirLink ES, GX, and LS devices has hardcoded root accounts, which makes it easier for remote attackers to obtain administrative access via a (1) SSH or (2) TELNET session." NVD's only Primary metric is CVSS v2 10.0 (AV:N/AC:L/Au:N/C:C/I:C/A:C); the record predates CVSS v3 and carries no v3 score. NVD files it under CWE-200, while the CERT/CC vulnerability note classes it as CWE-259 (use of hard-coded password), which describes the flaw better. The record was published on 2015-08-08 with CERT/CC as the CNA (NVD, CVE record).
Which gateways and ALEOS versions are affected?
CERT/CC VU#628568 (released 2015-08-07) says Sierra Wireless GX, ES and LS gateways running ALEOS 4.4.1 and earlier contain multiple hard-coded accounts with root privileges. The detail matters for older fleets: on ALEOS 4.3.4 and earlier the accounts are enabled by default and reachable over Telnet or SSH; in 4.3.5 to 4.4.1 the accounts still exist and are enabled, but remote access is off by default. NVD's CPE data matches ALEOS up to and including 4.4.1 on the AirLink ES440, ES450, GX440, GX450 and LS300.
How severe is it?
CERT/CC scores it CVSS v2 base 10.0, temporal 8.3 (E:F/RL:OF/RC:C, functional exploit code, official fix). The impact line in the note is plain: a remote, unauthenticated attacker may be able to gain full control of an affected device. On a cellular gateway that is the path into everything behind it, from RTUs and PLCs at a remote site to the management VPN.
How do you fix or mitigate it?
CERT/CC says Sierra Wireless released ALEOS 4.4.2, which addresses the issue by disabling access to the hard-coded accounts by default; Sierra Wireless published a technical bulletin for CVE-2015-2897 on 2015-08-07. Where an update is not possible, CERT/CC advises allowing connections only from trusted hosts and networks. In practice that means Telnet off, SSH limited to a management network or VPN, and no management ports on the cellular WAN. The note describes the fix as a change of default, so also check the SSH and Telnet settings on units that were configured by hand.
Our Sierra Wireless AirLink router guide covers the ALEOS release lines and which management services to check, and the hard-coded credentials fix guide explains why per-device secrets matter. Later ALEOS releases had similar issues: the SNMP-triggered hard-coded account CVE-2018-4062 and the root password hash exposure CVE-2023-40463. The unauthenticated remote code execution flaw CVE-2018-10251 and the RPC server flaw CVE-2020-8782 hit the same ES, GX and LS hardware. To find which gateways still run an old ALEOS build, Device & Firmware Security matches components and versions against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories.
CVE-2015-2897 is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.02214, the 83.1st percentile, in the 2026-11-20 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD (read 2026-11-21): status Modified; published 2015-08-08; NVD Primary CVSS v2 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C, no CVSS v3 metric; CWE-200 (NVD); CPE ALEOS up to and including 4.4.1 on AirLink ES440, ES450, GX440, GX450 and LS300; reference CERT/CC VU#628568. — NVD
- CERT/CC VU#628568 (released 2015-08-07, revised 2015-08-10), read 2026-11-21: GX, ES and LS gateways on ALEOS 4.4.1 and earlier contain multiple hard-coded root accounts, CWE-259; accounts enabled by default and reachable by Telnet or SSH on 4.3.4 or earlier, still enabled in 4.3.5 to 4.4.1 with remote access disabled by default; ALEOS 4.4.2 disables access to the accounts by default; workaround: restrict access to trusted hosts and networks; CVSS v2 base 10, temporal 8.3. — CERT/CC VU#628568
- Sierra Wireless Source page "Technical Bulletin - CVE-2015-2897", dated 2015-08-07, read 2026-11-21 (bulletin download behind the page). — Sierra Wireless
- CVE record (checked 2026-11-21): state PUBLISHED, CNA CERT/CC, published 2015-08-08; no CNA CVSS metric. — CVE.org
- Not in the CISA KEV catalog, version 2026.11.20 (1,790 entries), checked 2026-11-21. — CISA KEV
- EPSS 0.02214, percentile 0.83054, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which ALEOS version fixes CVE-2015-2897?
ALEOS 4.4.2. CERT/CC says Sierra Wireless addressed the issue in 4.4.2 by disabling access to the hard-coded accounts by default. All releases up to and including 4.4.1 on AirLink GX, ES and LS gateways are affected (per CERT/CC VU#628568 and NVD).
Is a gateway on ALEOS 4.4.0 or 4.4.1 exposed by default?
Less so than older units. CERT/CC says the accounts exist and are enabled in ALEOS 4.3.5 to 4.4.1, but remote access is disabled by default there; on 4.3.4 and earlier the accounts are reachable over Telnet or SSH out of the box. A unit where someone turned Telnet or SSH on is exposed either way.
What can I do if a gateway cannot be updated?
CERT/CC recommends allowing connections only from trusted hosts and networks. Turn Telnet off, keep SSH reachable only from a management network or VPN, and make sure no management service listens on the cellular WAN. Plan to replace the unit if it cannot run 4.4.2 or later.
Why does NVD list CWE-200 when the flaw is a hard-coded password?
NVD assigned CWE-200 (information exposure) when it analysed the record in 2015. The CERT/CC note, written by the coordinator of the disclosure, classes it as CWE-259, use of hard-coded password, which matches the description of built-in root accounts.
Questions about this page?