Debian LinuxOperating system · Debian

CVE-2017-5383

MEDIUM · 5.3 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 45.7.0 / 51.0 or later.
See remediation →
62/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
URLs containing certain unicode glyphs for alternative hyphens and quotes do not properly trigger punycode display, allowing for domain name spoofing attacks in the location bar. This vulnerability affects Thunderbird < 45.7, Firefox ESR < 45.7, and Firefox < 51.

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

Mozilla browsers fail to properly display punycode for URLs containing unicode glyphs that resemble standard hyphens and quotes, enabling attackers to spoof domain names in the location bar and trick users into believing they're on a legitimate website.

MitigationUpgrade to Firefox 51+, Firefox ESR 45.7+, or Thunderbird 45.7+ to resolve the unicode/punycode handling issue.

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
Debian LinuxOperating system
Affected:= 8.0
Enterprise LinuxOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.3= 7.4
Enterprise Linux Server EusOperating system
Affected:= 7.3= 7.4= 7.5
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0= 7.0
FirefoxWeb browser
Affected:< 51.0< 45.7.0

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check if Firefox is installed
    Run 'which firefox' or check your package manager for installed Firefox packages (e.g., 'rpm -qa | grep -i firefox' on RHEL, 'dpkg -l | grep -i firefox' on Debian)
    Affected if Firefox is not installed on the system
  2. Determine installed Firefox version
    Run 'firefox --version' or check via package manager ('rpm -q firefox' on RHEL, 'dpkg -s firefox' on Debian)
    Affected if Command fails or returns no version information (Firefox may be installed but not accessible in PATH)
  3. Compare version against affected ranges
    For standard Firefox: any version below 51.0 is affected. For ESR: any version below 45.7.0 is affected. Identify ESR by checking 'firefox --version' output for 'ESR' label or checking package name (e.g., firefox-esr)
    Affected if Firefox version is below 51.0 (standard) or below 45.7.0 (ESR)
  4. Verify browser is used on the system
    Check if Firefox is set as default browser or frequently used: look for desktop shortcuts, recent usage in ~/.local/share/applications, or check 'xdg-mime query default' for default browser
    Affected if Firefox is the primary or commonly used browser on this system

You are affected if Firefox (standard version below 51.0 or ESR version below 45.7.0) is installed and used as a browser on your Debian 8.0 or RHEL 5/6/7 system.

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 45.7.0 / 51.0 or later
Fixed in 45.7.051.0
Interim mitigation

Upgrade to Firefox 51+, Firefox ESR 45.7+, or Thunderbird 45.7+ to resolve the unicode/punycode handling issue.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5383 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5383 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