dbcve.org
JunosOperating system · Juniper

CVE-2016-1273

MEDIUM · 5.9 CVSS v3.0 Published 2016-04-15
Fix available
A fix is available. Upgrade to after 13.2x51 or later.
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 13.2X51-D40, 14.x before 14.1X53-D30, and 15.x before 15.1X53-D20 on QFX5100 and QFX10002 switches do not have sufficient entropy, which makes it easier for remote attackers to defeat cryptographic encryption and authentication protection mechanisms via unspecified vectors.

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 · moderate confidence

The QFX5100 and QFX10002 switches running affected Junos OS versions have insufficient entropy sources, which weakens cryptographic operations. This allows attackers to potentially predict random values used in encryption keys or authentication mechanisms, compromising the security of encrypted sessions and authentication flows.

MitigationUpgrade Junos OS to version 13.2X51-D40 or later for 13.x, 14.1X53-D30 or later for 14.x, or 15.1X53-D20 or later for 15.x. Schedule maintenance window and test cryptographic functionality post-upgrade.

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:<= 13.2x51= 14.1x53= 15.1= 15.1x49= 15.1x53

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
High
Integrity
None
Availability
None

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

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 switch model
    Run `show chassis hardware` or `show system information` to confirm the device is a QFX5100 or QFX10002 switch
    Affected if Model is QFX5100 or QFX10002 and version matches affected ranges
  2. Check Junos OS version
    Run `show version` to display the installed Junos OS version
    Affected if Version is 13.2X51 or earlier, 14.1X53, 15.1, 15.1X49, or 15.1X53 (exact matches or lower for 13.2X51)
  3. Verify entropy configuration status
    Check if the device is using hardware RNG by reviewing `show system entropy` or `show chassis hardware` output for entropy module status
    Affected if Hardware entropy source is not present or not initialized (insufficient entropy for cryptographic operations)

Device is affected if it is a QFX5100 or QFX10002 running Junos OS version 13.2X51 or earlier, 14.1X53, 15.1, 15.1X49, or 15.1X53 and lacks proper entropy sources for cryptographic operations.

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
Upgrade available Upgrade to a release after 13.2x51
Interim mitigation

Upgrade Junos OS to version 13.2X51-D40 or later for 13.x, 14.1X53-D30 or later for 14.x, or 15.1X53-D20 or later for 15.x. Schedule maintenance window and test cryptographic functionality post-upgrade.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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