dbcve.org
JunosOperating system · Juniper

CVE-2016-1276

MEDIUM · 5.9 CVSS v3.0 Published 2016-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
Juniper Junos OS before 12.1X46-D50, 12.1X47 before 12.1X47-D23, 12.3X48 before 12.3X48-D25, and 15.1X49 before 15.1X49-D40 on a High-End SRX-Series chassis system with one or more Application Layer Gateways (ALGs) enabled allow remote attackers to cause a denial of service (CPU consumption, fab link failure, or flip-flop failovers) via vectors related to in-transit traffic matching ALG rules.

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 Junos OS on High-End SRX-Series chassis systems allows remote attackers to cause excessive CPU consumption, fab link failure, or flip-flop failovers via specially crafted in-transit traffic that matches Application Layer Gateway (ALG) rules.

MitigationUpgrade Junos OS to version 12.1X46-D50 or later, 12.1X47-D23 or later, 12.3X48-D25 or later, or 15.1X49-D40 or later. If immediate patching is not feasible, consider disabling unused ALGs to reduce attack surface.

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.1x46= 12.1x47= 12.3x48= 15.1x49

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

CVSS:3.0/AV:N/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 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 a High-End SRX-Series chassis system (SRX5600, SRX5800, or similar). This vulnerability only affects High-End SRX chassis platforms, not branch or mid-range SRX devices.
    Affected if The device is NOT a High-End SRX-Series chassis system - if so, this CVE does not apply.
  2. Check Junos OS version
    Run 'show version' to display the installed Junos OS version and build number. Compare the exact version and build to the affected ranges: 12.1X46 (all builds prior to D50), 12.1X47 (all builds prior to D23), 12.3X48 (all builds prior to D25), and 15.1X49 (all builds prior to D40).
    Affected if The installed Junos version falls within the affected version ranges and the device is a High-End SRX chassis system.
  3. Verify ALG services are enabled
    Run 'show services alg status' to check which Application Layer Gateway (ALG) protocols are enabled. Common ALGs include FTP, H.323, SIP, RTSP, and others. The vulnerability is triggered when specially crafted traffic matches active ALG rules.
    Affected if ALG services are enabled and the device meets the version criteria - this is the condition required for the vulnerability to be exploitable.
  4. Check for active ALG bindings in security policies
    Run 'show security policies' and review policy configurations to identify if any policies have ALG applications attached. The DoS triggers specifically when crafted in-transit traffic matches ALG-enabled policies.
    Affected if There are active security policies with ALG applications configured and the device is an affected version - this confirms the attack surface exists.

A user is affected if they are running a High-End SRX-Series chassis system with a Junos version in the affected ranges AND have ALG services enabled or configured in security policies.

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 version 12.1X46-D50 or later, 12.1X47-D23 or later, 12.3X48-D25 or later, or 15.1X49-D40 or later. If immediate patching is not feasible, consider disabling unused ALGs to reduce attack surface.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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