dbcve.org
JunosOperating system · Juniper

CVE-2020-1684

HIGH · 7.5 CVSS v3.1 Published 2020-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
On Juniper Networks SRX Series configured with application identification inspection enabled, receipt of specific HTTP traffic can cause high CPU load utilization, which could lead to traffic interruption. Application identification is enabled by default and is automatically turned on when Intrusion Detection and Prevention (IDP), AppFW, AppQoS, or AppTrack is configured. Thus, this issue might occur when IDP, AppFW, AppQoS, or AppTrack is configured. This issue affects Juniper Networks Junos OS on SRX Series: 12.3X48 versions prior to 12.3X48-D105; 15.1X49 versions prior to 15.1X49-D221, 15.1X49-D230; 17.4 versions prior to 17.4R3-S3; 18.1 versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S3; 18.3 versions prior to 18.3R2-S4, 18.3R3-S2; 18.4 versions prior to 18.4R2-S5, 18.4R3-S1; 19.1 versions prior to 19.1R2-S2, 19.1R3; 19.2 versions prior to 19.2R1-S5, 19.2R2; 19.3 versions prior to 19.3R3; 19.4 versions prior to 19.4R2.

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 denial-of-service vulnerability in Juniper SRX Series firewalls allows specific HTTP traffic to trigger high CPU utilization when application identification inspection is enabled (default when IDP, AppFW, AppQoS, or AppTrack are configured), potentially causing traffic interruption.

MitigationUpgrade Junos OS to the fixed versions specified in the advisory. Alternatively, if immediate upgrade is not feasible, consider disabling AppID-related features (IDP, AppFW, AppQoS, AppTrack) if business requirements allow.

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.4= 18.1= 18.2= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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. Confirm device is Juniper SRX Series
    Run 'show chassis hardware' or 'show system information' to identify the device model
    Affected if Device is not an SRX Series firewall (not affected)
  2. Check Junos OS version
    Run 'show version' and compare the installed version against the affected list: 12.3x48, 15.1x49, 17.4, 18.1, 18.2, 18.3, 18.4, 19.1, 19.2, 19.3, 19.4
    Affected if Version matches one of the affected releases listed in the advisory
  3. Check if IDP (Intrusion Detection and Prevention) is enabled
    Run 'show security idp status' - if the command succeeds and shows IDP as active, IDP is enabled
    Affected if IDP is enabled and version is affected
  4. Check if AppFW (Application Firewall) is enabled
    Run 'show security application-firewall status' - if configuration exists and is active, AppFW is enabled
    Affected if AppFW is enabled and version is affected
  5. Check if AppQoS is enabled
    Run 'show class-of-service application-traffic-controller' - if configuration exists, AppQoS is enabled
    Affected if AppQoS is enabled and version is affected
  6. Check if AppTrack is enabled
    Run 'show security application-tracking status' - if configuration exists, AppTrack is enabled
    Affected if AppTrack is enabled and version is affected

A user is affected if they have an SRX Series firewall running an affected Junos version (12.3x48, 15.1x49, 17.4, 18.1-18.4, or 19.1-19.4) with any AppID-related feature (IDP, AppFW, AppQoS, or AppTrack) currently enabled.

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

Upgrade Junos OS to the fixed versions specified in the advisory. Alternatively, if immediate upgrade is not feasible, consider disabling AppID-related features (IDP, AppFW, AppQoS, AppTrack) if business requirements allow.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1684 — 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-2020-1684 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