Skip to content

Vulnerabilities

HighKEV

CVE-2017-6742 — Cisco IOS and IOS XE Software SNMP Remote Code Execution Vulnerability

CVE-2017-6742 · Cisco IOS XE Software · CVSS 8.8 · KEV

In brief

Severity · CVSS
High8.8CVSS 3.1, High
EPSS
21%
CISA KEV
Known exploited, listed since 19 Apr 2023
CERT-FR
No advisory or alert referenced in the catalog
Vendor
Cisco
Published · Modified
·
Last verified

Summary

A vulnerability in the SNMP implementation of could allow an authenticated, remote attacker to cause a reload of the affected system or to remotely execute code. An attacker could exploit this vulnerability by sending a crafted SNMP packet to the affected device.  The vulnerability is due to a buffer overflow in the affected code area. The vulnerability affects all versions of SNMP (versions 1, 2c, and 3). The attacker must know the SNMP read only community string (SNMP version 2c or earlier) or the user credentials (SNMPv3). An exploit could allow the attacker to execute arbitrary code and obtain full control of the system or to cause a reload of the affected system. Only traffic directed to the affected system can be used to exploit this vulnerability.

Weakness: CWE-119

Title, description and the vendor's statements are quoted from the CVE record; a vendor's advisory is summarised in Patcharo's words, with a link.

Affected and fixed versions

Per product and release branch, as the vendor's CVE record and official advisory state them. A fixed release is shown only when a document names it: the vendor's, or CERT-FR's for Check Point, with its source.

16 branches without a precise fixed release

Cisco IOS XE Software

Source: CVE-2017-6742cisco-sa-20170629-snmp

  1. 16.5
    Affected versions16.5.1, 16.5.1b
    First fixed releaseNot published in the sources followed
  2. 16.4
    Affected versions16.4.1, 16.4.2
    First fixed releaseNot published in the sources followed
  3. 16.3
    Affected versions16.3.1, 16.3.1a, 16.3.2, 16.3.3
    5 releases listed16.3.1, 16.3.1a, 16.3.2, 16.3.3, 16.3.4
    First fixed releaseNot published in the sources followed
  4. 16.2
    Affected versions16.2.1, 16.2.2
    First fixed releaseNot published in the sources followed
  5. 3.18
    Affected versions3.18s, 3.18.1s
    First fixed releaseNot published in the sources followed
  6. 3.17
    Affected versions3.17s, 3.17.1s, 3.17.2s, 3.17.3s
    First fixed releaseNot published in the sources followed
  7. 3.16
    Affected versions3.16s, 3.16.1s, 3.16.2s, 3.16.3s
    5 releases listed3.16s, 3.16.1s, 3.16.2s, 3.16.3s, 3.16.5s
    First fixed releaseNot published in the sources followed
  8. 3.15
    Affected versions3.15s, 3.15.1s, 3.15.2s, 3.15.3s
    5 releases listed3.15s, 3.15.1s, 3.15.2s, 3.15.3s, 3.15.4s
    First fixed releaseNot published in the sources followed
  9. 3.14
    Affected versions3.14s, 3.14.1s, 3.14.2s, 3.14.3s
    5 releases listed3.14s, 3.14.1s, 3.14.2s, 3.14.3s, 3.14.4s
    First fixed releaseNot published in the sources followed
  10. 3.13
    Affected versions3.13s, 3.13.1s, 3.13.2s, 3.13.3s
    8 releases listed3.13s, 3.13.1s, 3.13.2s, 3.13.3s, 3.13.4s, 3.13.5s, 3.13.6s, 3.13.7s
    First fixed releaseNot published in the sources followed
  11. 3.12
    Affected versions3.12s, 3.12.1s, 3.12.2s, 3.12.3s
    5 releases listed3.12s, 3.12.1s, 3.12.2s, 3.12.3s, 3.12.4s
    First fixed releaseNot published in the sources followed
  12. 3.11
    Affected versions3.11s, 3.11.1s, 3.11.2s, 3.11.3s
    5 releases listed3.11s, 3.11.1s, 3.11.2s, 3.11.3s, 3.11.4s
    First fixed releaseNot published in the sources followed
  13. 3.9
    Affected versions3.9s, 3.9.1s, 3.9.2s
    First fixed releaseNot published in the sources followed
  14. 3.8
    Affected versions3.8s, 3.8.1s, 3.8.2s
    First fixed releaseNot published in the sources followed
  15. 3.7
    Affected versions3.7s, 3.7.1s, 3.7.2s, 3.7.3s
    10 releases listed3.7s, 3.7.1s, 3.7.2s, 3.7.3s, 3.7.4e, 3.7.4s, 3.7.5e, 3.7.5s, 3.7.6s, 3.7.7s
    First fixed releaseNot published in the sources followed
  16. 3.6
    Affected versions3.6.3e, 3.6.6e
    First fixed releaseNot published in the sources followed

The vendor states fixes are available; the releases per branch are in its advisory.

Remediation

Fix available

Vendor fix

Cisco has released updates that fix this vulnerability; its advisory lists them.

SourceCisco Security Advisory cisco-sa-20170629-snmp· revised 30 Jul 2025

Mitigation (vendor)

Cisco describes a workaround or a mitigation in its advisory.

SourceCisco Security Advisory cisco-sa-20170629-snmp

CISA KEV required action

Apply updates per vendor instructions.

CISA due date:

SourceCISA KEV

Last verified 1 Oct 2026 at 09:31 UTC

Known exploitation

Added to CISA KEV on 19 Apr 2023

Federal remediation due date: 10 May 2023

The CISA required action is shown under Remediation.

21% probability of exploitation in the next 30 days (percentile 98%).

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CERT-FR

No CERT-FR advisory or alert of the last two years references this CVE, for the vendors Patcharo covers.

Timeline

  1. Published by the source
  2. Added to CISA KEV
  3. CISA remediation due date
  4. Source record last modified
  5. EPSS score computed
  6. Last verified by Patcharo

Official sources

Cisco · CISA Known Exploited Vulnerabilities · NVD · FIRST EPSS · Cisco Security Advisory cisco-sa-20170629-snmp

How Patcharo reads this

Affected and fixed releases come from the vendor's structured statements and are matched against exact versions; CVSS from NVD, exploitation from CISA KEV and the vendor's own advisory, probability from FIRST EPSS. Missing data stays Unknown and never becomes Not affected.

Read the methodologyRead the guide: Cisco Secure Firewall release trains: Threat Defense, Management Center and ASA versions explained