CVE-2016-1279
No exploitation reported by the sources we read.
- Published2016-09-09
- WeaknessCWE-200 · CWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
J-Web in Juniper Junos OS before 12.1X46-D45, 12.1X46-D50, 12.1X47 before 12.1X47-D35, 12.3 before 12.3R12, 12.3X48 before 12.3X48-D25, 13.3 before 13.3R10, 13.3R9 before 13.3R9-S1, 14.1 before 14.1R7, 14.1X53 before 14.1X53-D35, 14.2 before 14.2R6, 15.1 before 15.1A2 or 15.1F4, 15.1X49 before 15.1X49-D30, and 15.1R before 15.1R3 might allow remote attackers to obtain sensitive information and consequently gain administrative privileges via unspecified vectors.
Timeline
dates in UTC- 2016-09-0914:05CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-1279?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-1279?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.1 | ≤ 12.1x46 | no fix published | NVD |
| 12.1 | = 12.1x46 | no fix published | NVD |
| 12.1 | = 12.1x47 | no fix published | NVD |
| 12.3 | = 12.3 | no fix published | NVD |
| 12.3 | = 12.3x48 | no fix published | NVD |
| 13.3 | = 13.3 | no fix published | NVD |
| 14.1 | = 14.1 | no fix published | NVD |
| 14.1 | = 14.1x53 | no fix published | NVD |
| 14.2 | = 14.2 | no fix published | NVD |
| 15.1 | = 15.1 | no fix published | NVD |
| 15.1 | = 15.1x49 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- kb.juniper.netVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- NVDweakness (CWE)CWE-200, CWE-287read 2026-10-23
- FIRST EPSSEPSS score2.9 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-09-09
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-1279?
Is CVE-2016-1279 actively exploited?
What is the CVSS score for CVE-2016-1279?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.