# CVE-2020-1652: Junos Space: OpenNMS is accessible via port 9443


- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Jul 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vf2p-4grj-v3x6

## What is CVE-2020-1652?

CVE-2020-1652 is a medium-severity vulnerability in Juniper Networks Junos Space, published on 17 Jul 2020. 

### Official description

OpenNMS is accessible via port 9443

Weakness: CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies)

## Which versions are affected by CVE-2020-1652?

It affects 1 product.


Products: Opennms Opennms.

## How do I fix CVE-2020-1652?

No fix has been published for CVE-2020-1652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1652 being exploited?

There is no known exploitation of CVE-2020-1652 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Networks Junos Space

- [CVE-2015-7856](https://insights.sbomify.com/CVE-2015-7856/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2016-6555](https://insights.sbomify.com/CVE-2016-6555/): OpenNMS Stored XSS via SNMP Trap Alerts (high 7.1)
- [CVE-2016-6556](https://insights.sbomify.com/CVE-2016-6556/): OpenNMS Stored XSS via SNMP Agent Data (high 7.1)
- [CVE-2014-3960](https://insights.sbomify.com/CVE-2014-3960/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-6095](https://insights.sbomify.com/CVE-2008-6095/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1652 and fix it if it is affected.

What it is: CVE-2020-1652 is a medium-severity vulnerability in Juniper Networks Junos Space, published on 17 Jul 2020. 
Exploitation: There is no known exploitation of CVE-2020-1652 in the wild and no public exploit code.

Affected product: Juniper Networks Junos Space. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1652/ (Markdown: https://insights.sbomify.com/CVE-2020-1652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1652
- OSV: https://osv.dev/vulnerability/CVE-2020-1652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1652/
Summaries are generated and may contain mistakes; the official description above is the record.