CVE-2014-5659
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 · uneditedThe ASTRO File Manager with Cloud (aka com.metago.astro) application ASTRO-4.4.592 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
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 confidenceThe ASTRO File Manager with Cloud Android application (com.metago.astro) version 4.4.592 fails to validate X.509 certificates from SSL servers during HTTPS connections. This allows man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates, enabling credential theft, data interception, and session hijacking when the app communicates with cloud services.
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= astro-4.4.592CVSS 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:M/Au:N/C:P/I:P/A:P
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.
-
Check if ASTRO File Manager is installedOn the Android device, go to Settings > Apps > Downloaded (or All) and look for 'ASTRO File Manager' or 'ASTRO File Manager With Cloud', or use ADB: adb shell pm list packages | grep astroAffected if The package com.metago.astro is present on the device
-
Identify the installed versionIn Settings > Apps > ASTRO File Manager, check the version under App Info, or use ADB: adb shell dumpsys package com.metago.astro | grep versionNameAffected if The version displayed is exactly 4.4.592
-
Verify HTTPS communication behaviorSince this is a certificate validation flaw in the app's code, the vulnerability is triggered when the app connects to cloud services over HTTPS. There is no local config to check - the flaw exists in how the app validates SSL certificates at the code level.Affected if The app makes HTTPS connections to cloud services while running version 4.4.592, making those connections vulnerable to MITM interception
The environment is affected if the ASTRO File Manager With Cloud app (com.metago.astro) version 4.4.592 is installed on the Android device and is used to access cloud services.
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 dataDevelopers must implement proper SSL/TLS certificate chain validation using Android's standard TrustManager API, including hostname verification and certificate chain trust evaluation. Users should update to a patched version and avoid transmitting sensitive data over untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5659 — 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-2014-5659 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