CVE-2018-0055
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 · uneditedReceipt of a specially crafted DHCPv6 message destined to a Junos OS device configured as a DHCP server in a Broadband Edge (BBE) environment may result in a jdhcpd daemon crash. The daemon automatically restarts without intervention, but a continuous receipt of crafted DHCPv6 packets could leaded to an extended denial of service condition. This issue only affects Junos OS 15.1 and later. Earlier releases are unaffected by this issue. Devices are only vulnerable to the specially crafted DHCPv6 message if DHCP services are configured. Devices not configured to act as a DHCP server are not vulnerable to this issue. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1R7-S2; 15.1X49 versions prior to 15.1X49-D160; 15.1X53 versions prior to 15.1X53-D235, 15.1X53-D495; 16.1 versions prior to 16.1R4-S11, 16.1R6-S6, 16.1R7-S2; 16.2 versions prior to 16.2R2-S7; 17.1 versions prior to 17.1R2-S9; 17.2 versions prior to 17.2R2-S6; 17.3 versions prior to 17.3R3-S1; 17.4 versions prior to 17.4R1-S5; 18.1 versions prior to 18.1R2-S3; 18.2 versions prior to 18.2R1-S2; 18.2X75 versions prior to 18.2X75-D20.
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 specially crafted DHCPv6 packet sent to a Junos OS device configured as a DHCP server in a Broadband Edge (BBE) environment triggers a buffer overflow or parsing error in the jdhcpd daemon, causing it to crash. While the daemon auto-restarts, sustained malicious packets create a persistent denial of service. Devices without DHCP server configuration or not in BBE environments are not affected.
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= 15.1= 15.1x49= 15.1x53= 16.1= 16.2= 17.1= 17.2= 17.3= 17.4= 18.2x75= 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:H/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.
-
Identify the Junos OS versionRun 'show version' or 'show version detail' on the device and note the software version stringAffected if The version matches one of the affected releases: 15.1, 15.1x49, 15.1x53, 16.1, 16.2, 17.1, 17.2, 17.3, 17.4, 18.2, or 18.2x75 series
-
Verify DHCPv6 server configurationRun 'show configuration | match dhcp' or 'show configuration protocols dhcpv6' to inspect DHCP server settingsAffected if DHCPv6 server service is explicitly configured on the device
-
Confirm Broadband Edge contextReview the device role and configuration context using 'show configuration system services dhcpv6' and check whether the device is deployed in a BBE/ broadband edge topologyAffected if The device operates in a Broadband Edge (BBE) environment with DHCPv6 services enabled
-
Monitor jdhcpd daemon stabilityRun 'show system processes extensive | match jdhcpd' or check system logs for daemon crash eventsAffected if The jdhcpd daemon is crashing repeatedly or showing instability
A device is affected if it runs an affected Junos version, has DHCPv6 server configured, and is deployed in a Broadband Edge environment, where specially crafted DHCPv6 packets can crash the jdhcpd daemon.
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 vendor-supplied Junos OS patches corresponding to the affected version lines (15.1R7-S2, 15.1X49-D160, 15.1X53-D235/D495, 16.1R4-S11/16.1R6-S6/16.1R7-S2, 16.2R2-S7, 17.1R2-S9, 17.2R2-S6, 17.3R3-S1, 17.4R1-S5, 18.1R2-S3, 18.2R1-S2, 18.2X75-D20 or later). As an interim measure, disable DHCPv6 server services on impacted devices or restrict management plane access via firewall filters.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0055 — 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-2018-0055 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