CVE-2017-10610

Name: CVE-2017-10610
Creator: NVD / NIST
Published: 2017-10-13T17:29:00.567+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.05%

Last modified Jun 17, 2026

CVE-2017-10610 is a vulnerability of currently unknown severity. On SRX Series devices, a crafted ICMP packet embedded within a NAT64 IPv6 to IPv4 tunnel may cause the flowd process to crash. Repeated crashes of the flowd process constitutes an extended denial of service condition for the SRX Series device. EPSS estimates a 1.05% chance of exploitation in the next 30 days.

Description

On SRX Series devices, a crafted ICMP packet embedded within a NAT64 IPv6 to IPv4 tunnel may cause the flowd process to crash. Repeated crashes of the flowd process constitutes an extended denial of service condition for the SRX Series device. This issue only occurs if NAT64 is configured. Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D71, 12.3X48 prior to 12.3X48-D55, 15.1X49 prior to 15.1X49-D100 on SRX Series. No other Juniper Networks products or platforms are affected by this issue.

Metrics

EPSS Probability

1.05%

60.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-20

Affected Software

Vendor	Product	Versions	Update
Juniper	Junos	12.1x46	—
Juniper	Junos	12.3x48	D10
Juniper	Junos	15.1x49	D10

References

https://kb.juniper.net/JSA10813Vendor Advisory
https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/nat-stateful-nat64-configuring.htmlVendor Advisory
https://kb.juniper.net/JSA10813Vendor Advisory
https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/nat-stateful-nat64-configuring.htmlVendor Advisory

Timeline

Published: Oct 13, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-10610?

How severe is CVE-2017-10610?

Severity scoring for CVE-2017-10610 is pending analysis. The EPSS model estimates a 1.05% probability of exploitation in the next 30 days.

How do I fix CVE-2017-10610?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-10610?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST