Junos Space: OpenNMS is accessible via port 9443

published 2020-07-17 6y ago modified 2026-06-17 4mo ago also EUVD-2020-12517

cvss: 5.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

OpenNMS is accessible via port 9443

Patch / fix

fixed in 1

Juniper Networks Junos Space 20.1R1

Is CVE-2020-1652 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.6	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

Juniper Networks Junos Space

Classification

Weakness

CWE-213 Exposure of Sensitive Information Due to Incompatible Policies

References

kb.juniper.net /
vendor-advisory

Sources

CVE List CVE-2020-1652
NVD CVE-2020-1652

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.