dbcve.org
JunosOperating system · Juniper

CVE-2019-0015

MEDIUM · 5.4 CVSS v3.1 Published 2019-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A token caching error in Juniper SRX Series dynamic VPN allows deleted users to continue establishing VPN connections until device reboot. When a dynamic VPN user is deleted from the system, their previously cached authentication token remains valid, bypassing access revocation controls.

MitigationApply the appropriate Junos OS patch for the affected version branch (12.3X48-D75+, 15.1X49-D150+, 17.3R3+, 17.4R2+, 18.1R3+, 18.2R2+) to remediate the token caching flaw; reboot the device as a temporary mitigation to clear cached tokens.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 12.3x48= 15.1x49= 17.3= 17.4= 18.1= 18.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Run 'show chassis hardware' or 'show system information' to confirm the device is an SRX Series model (SRX100, SRX110, SRX210, SRX240, SRX340, SRX345, SRX550, SRX650, etc.)
    Affected if Device is not an SRX Series device - this CVE only affects SRX Series dynamic VPN
  2. Check Junos version
    Run 'show version' and compare the full firmware version against the affected ranges: 12.3X48, 15.1X49, 17.3, 17.4, 18.1, 18.2
    Affected if The installed Junos version matches one of the affected version branches (exact versions listed in CVE details)
  3. Verify dynamic VPN is configured
    Run 'show configuration | display set | match dynamic-vpn' to check if dynamic VPN is enabled on the device
    Affected if Dynamic VPN is not configured - the vulnerability only applies when dynamic VPN feature is enabled
  4. Identify active dynamic VPN sessions
    Run 'show services dynamic-vpn sessions' to list all currently active dynamic VPN sessions
    Affected if No active sessions - the flaw allows deleted users to maintain sessions, so active sessions may include users who should no longer have access
  5. Compare active sessions against current user database
    Run 'show configuration system login user' to list configured users, then cross-reference with active sessions from step 4. Check if any active session user does not appear in the current user configuration
    Affected if Active session exists for a user that is no longer defined in the current configuration - this indicates the token caching flaw is being exploited

A user is affected if the device is an SRX Series running an affected Junos version with dynamic VPN enabled and an active session exists for a deleted user.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Junos OS patch for the affected version branch (12.3X48-D75+, 15.1X49-D150+, 17.3R3+, 17.4R2+, 18.1R3+, 18.2R2+) to remediate the token caching flaw; reboot the device as a temporary mitigation to clear cached tokens.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0015 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data