CVE-2017-10904
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 · uneditedQt for Android prior to 5.9.0 allows remote attackers to execute arbitrary OS commands via unspecified vectors.
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 command injection vulnerability in Qt for Android versions prior to 5.9.0 allows remote attackers to execute arbitrary operating system commands. The specific attack vector is not detailed in the advisory, but the vulnerability enables complete remote compromise of affected devices.
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< 5.9.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Qt for Android usageExamine the application's APK or installed files for Qt Core libraries (libQt5Core.so) and confirm the target platform is Android. Check build artifacts, manifest files, or library directories for Qt components.Affected if Qt libraries are present and the application targets Android platform
-
Determine Qt library versionLocate the Qt core libraries in the application package or system. Use commands like 'strings libQt5Core.so | grep -i version' or inspect version metadata embedded in the Qt libraries. Alternatively, query the library directly if runtime access is available.Affected if The extracted Qt version string indicates a version lower than 5.9.0
-
Verify command injection attack surfaceReview application code or behavior for any mechanisms that could pass user-controlled data to Qt functions that execute system commands. This may include URL handling, file processing, or inter-process communication pathways.Affected if The application processes external input through Qt APIs that could trigger command execution and Qt version is below 5.9.0
-
Confirm Android contextVerify the application runs on Android and uses Qt framework. Check application metadata, library dependencies, or runtime environment for Android-specific Qt components.Affected if Application runs on Android with Qt version prior to 5.9.0
The environment is affected if Qt for Android is deployed with a version earlier than 5.9.0 and the application has any attack surface that could trigger command injection through Qt APIs.
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.
dbcve · scoped5.9.0
Upgrade Qt for Android to version 5.9.0 or later. If upgrading is not immediately feasible, minimize exposure by restricting network access to affected applications and monitoring for malicious activity.
Qt 5.9.0 or later (Qt for Android)
- 1. Identify all Qt projects targeting Android in your environment
- 2. For each affected project, download and install Qt 5.9.0 or later from the official Qt website (qt.io)
- 3. Rebuild all Qt Android applications using Qt 5.9.0 or newer
- 4. Redeploy the rebuilt applications to all affected Android devices
- 5. Verify that the updated applications function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10904 — 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-10904 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