CVE-2017-2695
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 · uneditedTIT-AL00C583B211 has a directory traversal vulnerability which allows an attacker to obtain the files in email application.
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 confidenceA directory traversal vulnerability in the TIT-AL00C583B211 firmware allows attackers to use path traversal sequences (such as ../) to access files outside the email application's intended directory boundaries, enabling unauthorized retrieval of sensitive email data and related files stored on the device.
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= c583b211CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck if the device is a Huawei model TIT-AL00 by accessing device settings > About Phone > Model Number, or via adb shell getprop ro.product.modelAffected if Device model is not Huawei TIT-AL00 (unaffected)
-
Check firmware versionNavigate to Settings > About Phone > Version Number, or use adb shell getprop ro.build.version.emui to view the EMUI firmware versionAffected if Firmware version is NOT exactly c583b211 (not affected)
-
Confirm email application presenceCheck if the native email application is installed by viewing installed apps in Settings > Apps, or list packages via adb shell pm list packages | grep -i emailAffected if Email application is not installed (vulnerability not applicable)
-
Verify email app handles external contentCheck if the email application is configured with any email accounts or has capability to process email attachments/content. This can be verified by examining if the app has created any local storage directories for email data.Affected if Email app has never been used or configured (no attack vector)
-
Inspect email app directory permissionsUse a file manager or adb shell to examine the email application's private directory (typically /data/data/com.android.email or similar) and verify it allows external access patternsAffected if Directory traversal sequences (..%2f or ../) can be used within email app file operations to escape the intended directory
The environment is affected only if the device is Huawei TIT-AL00 with firmware version exactly c583b211, the native email application is installed and has been used to process email content, enabling path traversal within the email app's file handling.
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 dataApply the vendor firmware update from Huawei that addresses this path traversal issue; until then, restrict device access to trusted networks and avoid processing sensitive email content on affected devices.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.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,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2695 — 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-2695 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