# CVE-2020-1616: JATP Series: JATP Is susceptible to slow brute force attacks on the SSH service.

> An unauthenticated remote attacker can bypass SSH login attempt limits to perform brute-force password attacks on Juniper JATP devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7vpp-24rh-p2mv

## What is CVE-2020-1616?

CVE-2020-1616 is a medium-severity authentication bypass vulnerability in Juniper Networks JATP, published on 8 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to insufficient server-side login attempt limit enforcement, a vulnerability in the SSH login service of Juniper Networks Juniper Advanced Threat Prevention (JATP) Series and Virtual JATP (vJATP) devices allows an unauthenticated, remote attacker to perform multiple login attempts in excess of the configured login attempt limit. Successful exploitation will allow the attacker to perform brute-force password attacks on the SSH service. This issue affects: Juniper Networks JATP and vJATP versions prior to 5.0.6.0.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 2 products.


Products: Juniper Advanced Threat Protection, Juniper Virtual Advanced Threat Protection.

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

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

## Is CVE-2020-1616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1616 is a medium-severity authentication bypass vulnerability in Juniper Networks JATP, published on 8 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1616 in the wild and no public exploit code.

Affected product: Juniper Networks JATP. 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-1616/ (Markdown: https://insights.sbomify.com/CVE-2020-1616/index.md)
```

## Sources

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

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