How severe is CVE-2017-6742?

No CVSS score has been assigned to CVE-2017-6742 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2017-6742?

Affected package information for CVE-2017-6742 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-6742?

No fixed release is recorded for CVE-2017-6742 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2017-6742 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2017-6742 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2017-6742 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2017-6742, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-6742?

CVE-2017-6742 has an EPSS (Exploit Prediction Scoring System) score of 21.4%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2017-6742 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-6742 (Cisco IOS and IOS XE Software SNMP Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-04-19. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-05-10. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-6742?

CVE-2017-6742 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2017-6742 published, and has it been updated?

CVE-2017-6742 was published on July 17, 2017 and was last updated on January 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2017-6742

CVE-2017-6742 is a Buffer Overflow vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-04-19) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Jul 17, 2017

Updated

Jan 12, 2026

Affected

2 products

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-04-19. Federal agencies were required to remediate by 2023-05-10.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-6742.

EPSS Exploitation Probability

via FIRST.org ↗

21.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

2 products · 3 configurations

ioscisco

≥ 15.0 && ≤ 15.6

range

ios xecisco

≥ 2.2.0 && ≤ 3.17

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Simple Network Management Protocol (SNMP) subsystem of Cisco IOS 12.…

cisa.govCISAApr 2023

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2017-6742 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2017-6742 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works