CVE-2017-16813
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 · uneditedA denial-of-service issue was discovered in the Foxit MobilePDF app before 6.1 for iOS. This occurs when a user uploads a file that includes a hexadecimal Unicode character in the "filename" parameter via Wi-Fi, since the app could fail to parse this.
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 confidenceA denial-of-service vulnerability in Foxit MobilePDF iOS versions before 6.1 allows attackers to crash the app by uploading files with hexadecimal Unicode characters in the filename parameter via Wi-Fi. The app fails to properly parse the Unicode characters during the file upload process, causing a crash or failure.
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<= 6.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Foxit MobilePDF iOS app versionOpen the iOS App Store, go to the app listing for Foxit MobilePDF, or check the version in your purchase history. On the device: open the App Store app, tap your profile, tap Purchased, find Foxit MobilePDF, and check the version number shown.Affected if The installed version is 6.0.0 or earlier (any version <= 6.0.0)
-
Confirm the Wi-Fi transfer feature is in useCheck if the Wi-Fi transfer/web server feature has been enabled in the app settings. This feature allows file uploads over Wi-Fi and is typically found under Settings > Wi-Fi Transfer or a similar menu option within the app.Affected if Wi-Fi transfer is enabled and the app is listening for uploads
-
Identify the upload mechanismThe vulnerability is triggered when uploading files via the built-in Wi-Fi web server. When a file with hexadecimal Unicode characters in its filename is submitted through the web upload interface, the parsing failure occurs.Affected if Files are being uploaded via Wi-Fi with Unicode characters in filenames
-
Verify Unicode character presence in uploaded filesInspect the filenames of documents intended for upload. Files with hexadecimal Unicode characters (non-ASCII characters encoded in hex format) in their names would trigger the parsing failure during Wi-Fi upload.Affected if Files containing hexadecimal Unicode characters in filenames are uploaded via Wi-Fi
You are affected if Foxit MobilePDF iOS version is 6.0.0 or earlier AND you use the Wi-Fi transfer feature to upload files with Unicode characters in their filenames.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Foxit MobilePDF version 6.1 or later, which contains the fix for proper handling of Unicode characters in filenames during Wi-Fi file uploads.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16813 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-16813 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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