CVE-2020-1641
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 · uneditedA Race Condition vulnerability in Juniper Networks Junos OS LLDP implementation allows an attacker to cause LLDP to crash leading to a Denial of Service (DoS). This issue occurs when crafted LLDP packets are received by the device from an adjacent device. Multiple LACP flaps will occur after LLDP crashes. An indicator of compromise is to evaluate log file details for lldp with RLIMIT. Intervention should occur before 85% threshold of used KB versus maximum available KB memory is reached. show log messages | match RLIMIT | match lldp | last 20 Matching statement is " /kernel: %KERNEL-[number]: Process ([pid #],lldpd) has exceeded 85% of RLIMIT_DATA: " with [] as variable data to evaluate for. This issue affects: Juniper Networks Junos OS: 12.3 versions prior to 12.3R12-S15; 12.3X48 versions prior to 12.3X48-D95; 15.1 versions prior to 15.1R7-S6; 15.1X49 versions prior to 15.1X49-D200; 15.1X53 versions prior to 15.1X53-D593; 16.1 versions prior to 16.1R7-S7; 17.1 versions prior to 17.1R2-S11, 17.1R3-S2; 17.2 versions prior to 17.2R1-S9, 17.2R3-S3; 17.3 versions prior to 17.3R2-S5, 17.3R3-S6; 17.4 versions prior to 17.4R2-S4, 17.4R3; 18.1 versions prior to 18.1R3-S5; 18.2 versions prior to 18.2R2-S7, 18.2R3; 18.2X75 versions prior to 18.2X75-D12, 18.2X75-D33, 18.2X75-D50, 18.2X75-D420; 18.3 versions prior to 18.3R1-S7, 18.3R2-S3, 18.3R3; 18.4 versions prior to 18.4R1-S5, 18.4R2; 19.1 versions prior to 19.1R1-S4, 19.1R2.
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 confidenceA race condition in the Junos OS LLDP (Link Layer Discovery Protocol) implementation allows an adjacent attacker to send crafted LLDP packets that cause the lldpd process to crash, resulting in Denial of Service. The crash is preceded by the process exceeding 85% of RLIMIT_DATA memory, and causes cascading LACP (Link Aggregation Control Protocol) flaps on affected interfaces.
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= 12.3= 12.3x48= 15.1= 15.1x49= 15.1x53= 16.1= 17.1= 17.2= 17.3= 17.4= 18.1= 18.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Verify LLDP is enabled on the deviceRun 'show protocols lldp' or check interface configurations for 'set protocols lldp' entries. On Junos, use 'show lldp diagnostics' to see LLDP status.Affected if LLDP is enabled on any interface - the vulnerability only affects systems where LLDP is running
-
Confirm the Junos OS versionRun 'show version' or 'show version detail' to obtain the installed Junos version.Affected if The installed version matches one of: 12.3, 12.3x48, 15.1, 15.1x49, 15.1x53, 16.1, 17.1, 17.2, 17.3, 17.4, 18.1, or 18.2
-
Check for lldpd process restarts or crashesRun 'show system processes extensive | match lldpd' to view lldpd process status. Review logs with 'show log messages' for 'lldpd' crash entries.Affected if The lldpd process has crashed or shows frequent restarts, especially if accompanied by memory exhaustion indicators
-
Look for RLIMIT_DATA memory warning indicatorsReview system logs for messages containing 'RLIMIT' or '85%' related to the lldpd process. Use 'show log messages | match "lldpd"| match "RLIMIT"'.Affected if Logs show lldpd process exceeding 85% of RLIMIT_DATA memory before crashes
-
Check for LACP interface flapsRun 'show lacp interfaces' or review logs for 'LACP' flap messages on aggregated ethernet interfaces.Affected if Unusual LACP flaps are occurring on interfaces, which may indicate cascading effects from lldpd crashes
A device is likely affected if it runs a vulnerable Junos version (12.3 through 18.2), has LLDP enabled, and shows lldpd process crashes or memory pressure indicators.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the appropriate Junos OS software patch from the vendor's advisory. Until patched, monitor logs for the RLIMIT indicator and consider disabling LLDP on untrusted or external-facing interfaces to reduce attack surface.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-1641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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