No exploitation reported

CVE-2017-2303

No exploitation reported by the sources we read.

Published2017-05-30

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

On Juniper Networks products or platforms running Junos OS 12.1X46 prior to 12.1X46-D50, 12.1X47 prior to 12.1X47-D40, 12.3 prior to 12.3R13, 12.3X48 prior to 12.3X48-D30, 13.2X51 prior to 13.2X51-D40, 13.3 prior to 13.3R10, 14.1 prior to 14.1R8, 14.1X53 prior to 14.1X53-D35, 14.1X55 prior to 14.1X55-D35, 14.2 prior to 14.2R5, 15.1 prior to 15.1F6 or 15.1R3, 15.1X49 prior to 15.1X49-D30 or 15.1X49-D40, 15.1X53 prior to 15.1X53-D35, and where RIP is enabled, certain RIP advertisements received by the router may cause the RPD daemon to crash resulting in a denial of service condition.

Timeline

dates in UTC

2017-05-3014:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-2303?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-2303?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Juniper junos

Branch	Affected	Fixed in	Source
12.1	= 12.1x46	no fix published	NVD
12.1	= 12.1x47	no fix published	NVD
12.3	= 12.3	no fix published	NVD
12.3	= 12.3x48	no fix published	NVD
13.2	= 13.2x51	no fix published	NVD
13.3	= 13.3	no fix published	NVD
14.1	= 14.1	no fix published	NVD
14.1	= 14.1x53	no fix published	NVD
14.1	= 14.1x55	no fix published	NVD
14.2	= 14.2	no fix published	NVD
15.1	= 15.1	no fix published	NVD
15.1	= 15.1x49	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

kb.juniper.netVendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.07.5read 2026-10-23
NVDCVSS 2.07.8read 2026-10-23
FIRST EPSSEPSS score2.1 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published: 2017-05-30
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-2303?

Is CVE-2017-2303 actively exploited?

Active exploitation of CVE-2017-2303 has not been confirmed. Its EPSS score was 2.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-2303?

CVE-2017-2303 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database