# CVE-2019-0015: Junos OS: SRX Series: Deleted dynamic VPN users are allowed to establish VPN connections until reboot

> Deleted dynamic VPN users can bypass authentication and establish connections until the device is rebooted due to token caching errors.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c5qw-pgmj-mr6g

## What is CVE-2019-0015?

CVE-2019-0015 is a medium-severity authentication bypass vulnerability in Juniper Junos, published on 15 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the SRX Series Service Gateway allows deleted dynamic VPN users to establish dynamic VPN connections until the device is rebooted. A deleted dynamic VPN connection should be immediately disallowed from establishing new VPN connections. Due to an error in token caching, deleted users are allowed to connect once a previously successful dynamic VPN connection has been established. A reboot is required to clear the cached authentication token. Affected releases are Junos OS on SRX Series: 12.3X48 versions prior to 12.3X48-D75; 15.1X49 versions prior to 15.1X49-D150; 17.3 versions prior to 17.3R3; 17.4 versions prior to 17.4R2; 18.1 versions prior to 18.1R3; 18.2 versions prior to 18.2R2.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2019-0015?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2019-0015?

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

## Is CVE-2019-0015 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0015 and fix it if it is affected.

What it is: CVE-2019-0015 is a medium-severity authentication bypass vulnerability in Juniper Junos, published on 15 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0015 in the wild and no public exploit code.

Affected product: Juniper Junos. 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-2019-0015/ (Markdown: https://insights.sbomify.com/CVE-2019-0015/index.md)
```

## Sources

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

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