Security Advisory

CVE-2017-6046: Raven XE/XT Credential Sniffing

Last updated:
  • CVE-2017-6046

CVE-2017-6046 is a credential exposure flaw in Sierra Wireless AirLink Raven XE and Raven XT cellular gateways: sensitive information is not protected well enough in transit and can be sniffed by someone on the network path. NVD scores it 7.5 and CISA 4.3. CISA reports that Sierra Wireless will not address it, so network controls are the only mitigation.

Vulnerability summary

CVSS base score

7.5

High severity

EPSS score (FIRST)

1.6%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2017-6046 · Source: NVD

Affected components

ComponentCPEVersion range
Sierra Wireless AirLink Raven XEcpe:2.3:o:sierra_wireless:airlink_raven_xe_firmware:*:*:*:*:*:*:*:*CISA lists all versions before 4.0.14; Sierra Wireless reports it will not address this flaw, so 4.0.14 is not a fix for it (CISA ICSA-17-115-02)
Sierra Wireless AirLink Raven XTcpe:2.3:o:sierra_wireless:airlink_raven_xt_firmware:-:*:*:*:*:*:*:*CISA lists all versions before 4.0.11; Sierra Wireless reports it will not address this flaw, so 4.0.11 is not a fix for it (CISA ICSA-17-115-02)

What does this mean for affected devices?

NVD carries the ICS-CERT description: "Sensitive information is insufficiently protected during transmission and vulnerable to sniffing, which could lead to information disclosure." The ICS-CERT CNA classes it CWE-522 (insufficiently protected credentials); NVD uses CWE-200. The record was published on 2017-06-30 (NVD, CVE record).

How severe is it, and why do the scores differ?

NVD's Primary score is CVSS v3.0 7.5 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), with CVSS v2 5.0. CISA's ICSA-17-115-02 scores it 4.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N): CISA's vector requires user interaction and rates the disclosure as low. NVD assumes no user action and high confidentiality impact. Both agree that the flaw only leaks information and does not by itself change the device. In practice the severity depends on what the sniffed data unlocks: if it is the administrator password, the other Raven flaws and the device configuration are one step away.

Which gateways are affected, and is there a fix?

CISA lists the AirLink Raven XT, all versions before 4.0.11, and the AirLink Raven XE, all versions before 4.0.14, for all three Raven CVEs. The remediation text is clear, though: "Sierra Wireless reports that the insufficiently protected credentials vulnerability will not be addressed." The 4.0.14 and 4.0.11 releases fix the forced browsing and cross-site request forgery flaws, not this one. CISA credits Karn Ganeshen with the findings.

How do you mitigate it without a fix?

Treat every management session to a Raven gateway as readable by anyone on the path. Manage the units only over a VPN or a private APN, never across the open internet or a shared network, and keep the web interface off the cellular WAN. Use a password that is unique to the device, so a sniffed password does not open other gateways, and change it if it was ever used over an untrusted link. For a gateway this old, plan a replacement with a supported model.

The same advisory lists CVE-2017-6044 (files and directories reachable without authentication) and the cross-site request forgery CVE-2017-6042, both fixed in the firmware above. Our Sierra Wireless AirLink router guide covers the Raven and ALEOS lines and how to check management exposure, and the patch management guide covers what to do with devices that will receive no fix. Device & Firmware Security matches components and versions against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories.

CVE-2017-6046 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.01574, the 76.0th percentile, in the 2026-11-20 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD (read 2026-11-21): status Modified; published 2017-06-30; NVD Primary CVSS v3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, CVSS v2 5.0; CWE-200 (NVD), CWE-522 (ICS-CERT); reference ICSA-17-115-02. — NVD
  • CISA ICSA-17-115-02 CSAF (2017-04-25), read 2026-11-21: CVE-2017-6046 CWE-522, CVSS v3.0 4.3 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N; Raven XT before 4.0.11 and Raven XE before 4.0.14 listed; "Sierra Wireless reports that the insufficiently protected credentials vulnerability will not be addressed"; new firmware addresses the forced browsing and CSRF flaws; acknowledgment Karn Ganeshen. — CISA CSAF ICSA-17-115-02
  • CVE record (checked 2026-11-21): state PUBLISHED, CNA ICS-CERT, published 2017-06-30; CNA CWE-522, 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.01574, percentile 0.76032, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CISA CSAF: ICSA-17-115-02 Sierra Wireless AirLink Raven XE and XT (machine-readable advisory)
  3. CVE.org record CVE-2017-6046 (CNA: ICS-CERT)
  4. CISA KEV
  5. FIRST EPSS

Frequently asked questions

Does Raven XE 4.0.14 or Raven XT 4.0.11 fix CVE-2017-6046?

No. CISA ICSA-17-115-02 says the new firmware addresses the forced browsing and cross-site request forgery flaws, and that Sierra Wireless reports the insufficiently protected credentials flaw will not be addressed.

Why is the NVD score 7.5 and the CISA score 4.3?

CISA assumes a user has to take part and rates the disclosure as low (UI:R, C:L). NVD assumes no user action and a high confidentiality impact (UI:N, C:H). Both rate it as network-reachable and information-only.

How do I protect a Raven gateway that will never get a fix?

Manage it only over a VPN or private APN, keep the web interface off the cellular WAN, use a device-unique password and rotate it if it was ever used over an untrusted link. For long-term risk, replace the gateway with a supported model.