CVE-2015-5363
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 · uneditedThe SRX Network Security Daemon (nsd) in Juniper SRX Series services gateways with Junos 12.1X44 before 12.1X44-D50, 12.1X46 before 12.1X46-D35, 12.1X47 before 12.1X47-D25, and 12.3X48 before 12.3X48-D15 allows remote DNS servers to cause a denial of service (crash) via a crafted DNS response.
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 confidenceThe SRX Network Security Daemon (nsd) in Juniper SRX Series services gateways with specific Junos 12.1X44, 12.1X46, 12.1X47, and 12.3X48 releases crashes when processing a crafted DNS response from a remote DNS server, causing denial of service.
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.1x44= 12.1x46= 12.1x47= 12.3x48CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Check the Junos version installed on the SRX deviceRun 'show version' on the SRX CLI and locate the Junos version string (for example: 12.1X44-D40, 12.1X46-D30, etc.)Affected if The version matches exactly 12.1X44, 12.1X46, 12.1X47, or 12.3X48 with a build number earlier than D50, D35, D25, or D15 respectively (e.g., 12.1X44-D40 is affected, 12.1X44-D50 is not)
-
Confirm the nsd process is runningRun 'show system processes' or 'show system processes extensive' and look for the 'nsd' daemon in the process listAffected if The nsd process is present and running (this is the component that crashes when processing the malformed DNS response)
-
Verify DNS service is enabled or configuredRun 'show services dns' or 'show configuration services dns' to check if DNS proxy or DNS filtering services are configured on the deviceAffected if DNS services are enabled, as the vulnerability is triggered by processing DNS responses through these services
You are affected if your SRX device runs Junos version 12.1X44, 12.1X46, 12.1X47, or 12.3X48 with a build prior to the fixed releases (D50, D35, D25, D15) and has DNS services enabled, making the nsd daemon vulnerable to crashes from crafted DNS responses.
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 dataUpgrade Junos to the fixed versions: 12.1X44-D50 or later, 12.1X46-D35 or later, 12.1X47-D25 or later, or 12.3X48-D15 or later.
- Consultation3.0 h
- Implementation2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5363 — 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-2015-5363 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