dbcve.org
JunosOperating system · Juniper

CVE-2014-6447

HIGH · 7.1 CVSS v3.1 Published 2020-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Multiple vulnerabilities exist in Juniper Junos J-Web error handling that may lead to cross site scripting (XSS) issues or crash the J-Web service (DoS). This affects Juniper Junos OS 12.1X44 before 12.1X44-D45, 12.1X46 before 12.1X46-D30, 12.1X47 before 12.1X47-D20, 12.3 before 12.3R8, 12.3X48 before 12.3X48-D10, 13.1 before 13.1R5, 13.2 before 13.2R6, 13.3 before 13.3R4, 14.1 before 14.1R3, 14.1X53 before 14.1X53-D10, 14.2 before 14.2R1, and 15.1 before 15.1R1.

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

Multiple vulnerabilities in Juniper Junos J-Web error handling allow authenticated attackers to inject malicious scripts through error pages (XSS) or cause denial of service by crashing the J-Web service. The J-Web interface, used for web-based device management, fails to properly sanitize error outputs, enabling both script injection and service disruption attacks.

MitigationUpgrade Junos OS to one of the fixed versions (12.1X44-D45, 12.1X46-D30, 12.1X47-D20, 12.3R8, 12.3X48-D10, 13.1R5, 13.2R6, 13.3R4, 14.1R3, 14.1X53-D10, 14.2R1, or 15.1R1). If patching is not immediately feasible, disable J-Web or restrict management access to trusted networks via firewall policies.

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.1x44= 12.1x46= 12.1x47= 12.3= 12.3x48= 13.1= 13.2= 13.3= 14.1= 14.1x53= 14.2= 15.1

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Verify J-Web is enabled
    Run 'show system services web-management' or check the configuration for 'system services web-management'
    Affected if J-Web is enabled and accessible - the vulnerability only applies when J-Web is active
  2. Check Junos OS version
    Run 'show version' or 'request system version' to obtain the installed Junos release
    Affected if The installed version matches one of the affected versions: 12.1x44, 12.1x46, 12.1x47, 12.3, 12.3x48, 13.1, 13.2, 13.3, 14.1, 14.1x53, 14.2, or 15.1
  3. Confirm J-Web is accessible
    Attempt to access the J-Web interface via HTTPS or HTTP on the management interface port (typically 443 or 8443)
    Affected if The J-Web interface responds to HTTP/HTTPS requests

You are affected if J-Web is enabled and your Junos version matches any of the listed affected versions (12.1x44 through 15.1).

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 one of the fixed versions (12.1X44-D45, 12.1X46-D30, 12.1X47-D20, 12.3R8, 12.3X48-D10, 13.1R5, 13.2R6, 13.3R4, 14.1R3, 14.1X53-D10, 14.2R1, or 15.1R1). If patching is not immediately feasible, disable J-Web or restrict management access to trusted networks via firewall policies.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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